In situations like this, it would be good for the test runner to take a screenshot and add save it in files (when running in CI, later push that as artifact)
[0-0] Error in "LOGIN: user is able to login via gmail" 05:14
Error: Can't call setValue on element with selector "-ios class chain:**/XCUIElementTypeSecureTextField[`value == "Enter your pass phrase"`]" because element wasn't found 05:14
at CreateKeyScreen.fillPassPhrase (/Users/semaphore/git/flowcrypt-ios/appium/tests/screenobjects/create-key.screen.ts:33:35) 05:14
at CreateKeyScreen.setPassPhrase (/Users/semaphore/git/flowcrypt-ios/appium/tests/screenobjects/create-key.screen.ts:47:14) 05:14
at UserContext.<anonymous> (/Users/semaphore/git/flowcrypt-ios/appium/tests/specs/login/GmailLogin.spec.ts:13:25) 05:16
[0-0] RETRYING in /Users/semaphore/git/flowcrypt-ios/appium/FlowCrypt.app - /tests/specs/login/GmailLogin.spec.ts
That way we can debug it. Frequent retries slow down tests.
In situations like this, it would be good for the test runner to take a screenshot and add save it in files (when running in CI, later push that as artifact)
That way we can debug it. Frequent retries slow down tests.