Pretty slick! I wish we had this a long time ago. At the time, our testing infrastructure was a bunch of very flaky Selenium tests that we would run on through SauceLabs. The tests were super slow, mainly because we tried to reduce flakiness by buffering clicks/interactions with sleep() commands. All around, a painful experience which developers hated, which meant engineers did everything they could to avoid adding/m…
> we tried to reduce flakiness by buffering clicks/interactions with sleep()... You should have used waits instead of sleep. Wait pools until your DOM is in the state you are waiting it to be, unless given timeout occurs: https://www.selenium.dev/documentation/webdriver/waits/#expl...
It's been a while. I think we did use waits but they were still flakier than you might expect.