medium10 pts · first answer countsui-testingtest-reliability

Flaky UI test timing

An Espresso or XCUITest test fails randomly because it checks a label before a network-backed screen has finished loading. What is the best fix?

A.Add a fixed sleep of a few seconds before every check, tuned on the slowest CI machine, so the screen always has time to finish loading firstB.Wait for a condition (idling resources in Espresso, waitForExistence in XCUITest, waitUntil in Compose tests) and replace the real network with a fakeC.Retry the test until it passes and ignore failuresD.Delete the test, since UI tests are always flaky

Discussion 0

Join free to post in the discussion.

Flaky UI test timing

Discussion 0

Related questions