[Feature] Extend expect() timeout after it started waiting

I’d like way to extend the expect timeout similarly to how I can extend the test timeout:

testInfo.setTimeout(testInfo.timeout + 30000)

Use case

I’m testing a rate limited backend and sometimes it gets overloaded. In that case my tests need to wait 10-20 seconds, sometimes up to 60 seconds before a backend requests can successfully be retried. I don’t want to extend all expect timeouts to 60+ seconds as that would make failure detection very slow. But I can detect the backend rate limitation kicking in and in that case I already increase the test timeout. I’d like to do the same for the expect timeout.

This is the current function I use to extend the currently running test timeout

function tryToExtendPlaywrightTestTimeout(extendByMs: number) {
   test.info().setTimeout(testInfo.timeout + extendByMs)
   // would be nice to have a way to extend the timeout of the currently running expect(...) -- if one is running
}

[cassus]

It would work fine for success / Failure detection. The only drawback is the lack of the the more accurate expect failure error messages. The test timeout error messages are less detailed, harder to debug.

Along these lines I think setting the expect timeout sufficiently high (30-60 seconds) will avoid most of the congestion issues and still give me a more helpful error message. Thanks for the inspiration @aslushnikov !

[aslushnikov]

@cassus I’d recommend you to disable expect timeout via testProject.expect.timeout and only change the test timeout via testInfo.setTiemout.

Would this workaround work?