Some of our backend requests for our integration tests take longer to complete than others so we'd like to be able to control the max timeout before a given condition is expected to be true on a per test assertion basis. Without this we sometimes resort to Process.sleep which isn't ideal or create our own system to timeout/wait for a given css to be available on the page.
This applies to many Wallaby functions, but here are a few particular functions where configurable timeouts would be especially helpful:
Wallaby.Browser.click/2
Wallaby.Browser.assert_has/2
I think that Playwright's rich support for different types of timeouts could be a source of inspiration: https://playwright.dev/docs/test-timeouts
Some of our backend requests for our integration tests take longer to complete than others so we'd like to be able to control the max timeout before a given condition is expected to be true on a per test assertion basis. Without this we sometimes resort to
Process.sleepwhich isn't ideal or create our own system to timeout/wait for a given css to be available on the page.This applies to many Wallaby functions, but here are a few particular functions where configurable timeouts would be especially helpful:
Wallaby.Browser.click/2Wallaby.Browser.assert_has/2I think that Playwright's rich support for different types of timeouts could be a source of inspiration: https://playwright.dev/docs/test-timeouts