Monitor test duration

Description

Doc

Monitor test durations: Flex test timeouts to allow long running tests. We should have a long timeout which will kill stuck tests eventually. Tests should include durations for pod becoming ready, cluster becoming ready and we need to check these durations. Between two releases time to cluster readiness may change significantly and making this time longer should be considered as a regression.

  • Single test duration should be limited to 1h max (or maybe even 45min), if it’s longer split it into two or more tests. Reason: if the test fails somewhere at the end and you make some changes to fix it you need to wait a long time to check if it will pass or not.

Environment

None

Activity

Show:

Tomislav Plavcic March 15, 2023 at 6:25 PM

We have implemented test duration reports into dev pipelines and will keep monitoring and fixing the long running ones (which will be continuous task).

Done

Details

Assignee

Reporter

Needs QA

Yes

Priority

Smart Checklist

Created January 18, 2023 at 8:33 AM
Updated March 5, 2024 at 10:22 AM
Resolved March 15, 2023 at 6:23 PM