appium pass phrase entry failures

[tomholub]

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.

[fcvakintos]

@tomholub you have it even from beginning https://flowcrypt.semaphoreci.com/artifacts/jobs/0562b03f-fde1-439b-b1d2-379c9507133f?path=tmp

[tomholub]

Very good. I'll leave the issue open for potentially improving the pass phrase input testing.

[tomholub]

Also observed here https://flowcrypt.semaphoreci.com/jobs/4c33705f-7f5f-4e18-830b-99ee3da0f09b

Error: Can't call setValue on element with selector "-ios class chain:**/XCUIElementTypeSecureTextField[`value == "Enter your pass phrase"`]" because element wasn't found 08:45
    at CreateKeyScreen.fillPassPhrase (/Users/semaphore/git/flowcrypt-ios/appium/tests/screenobjects/create-key.screen.ts:33:35) 08:45
    at CreateKeyScreen.setPassPhrase (/Users/semaphore/git/flowcrypt-ios/appium/tests/screenobjects/create-key.screen.ts:47:14) 08:45
    at UserContext.<anonymous> (/Users/semaphore/git/flowcrypt-ios/appium/tests/specs/login/GmailLogin.spec.ts:13:25) 08:46
[0-0] FAILED in /Users/semaphore/git/flowcrypt-ios/appium/FlowCrypt.app - /tests/specs/login/GmailLogin.spec.ts (1 retries) 08:46
 "spec" Reporter: 08:46
------------------------------------------------------------------ 08:46
[iPhone 13 iOS 15.0 #0-0] Spec: /Users/semaphore/git/flowcrypt-ios/appium/tests/specs/login/GmailLogin.spec.ts 08:46
[iPhone 13 iOS 15.0 #0-0] Running: iPhone 13 on iOS 15.0 executing /Users/semaphore/git/flowcrypt-ios/appium/FlowCrypt.app 08:46
[iPhone 13 iOS 15.0 #0-0] Session ID: c1fbd4f4-238d-4eb3-a4e7-6dcf1eba42d7 08:46
[iPhone 13 iOS 15.0 #0-0] 08:46
[iPhone 13 iOS 15.0 #0-0] LOGIN: 08:46
[iPhone 13 iOS 15.0 #0-0]    ✖ user is able to login via gmail 08:46
[iPhone 13 iOS 15.0 #0-0] 08:46
[iPhone 13 iOS 15.0 #0-0] 1 failing (1m 43.3s) 08:46
[iPhone 13 iOS 15.0 #0-0] 08:46
[iPhone 13 iOS 15.0 #0-0] 1) LOGIN:  user is able to login via gmail 08:46
[iPhone 13 iOS 15.0 #0-0] Error: Can't call setValue on element with selector "-ios class chain:**/XCUIElementTypeSecureTextField[`value == "Enter your pass phrase"`]" because element wasn't found 08:46
[iPhone 13 iOS 15.0 #0-0] Error: Can't call setValue on element with selector "-ios class chain:**/XCUIElementTypeSecureTextField[`value == "Enter your pass phrase"`]" because element wasn't found 08:46
[iPhone 13 iOS 15.0 #0-0]     at CreateKeyScreen.fillPassPhrase (/Users/semaphore/git/flowcrypt-ios/appium/tests/screenobjects/create-key.screen.ts:33:35) 08:46
[iPhone 13 iOS 15.0 #0-0]     at CreateKeyScreen.setPassPhrase (/Users/semaphore/git/flowcrypt-ios/appium/tests/screenobjects/create-key.screen.ts:47:14) 08:46
[iPhone 13 iOS 15.0 #0-0]     at UserContext.<anonymous> (/Users/semaphore/git/flowcrypt-ios/appium/tests/specs/login/GmailLogin.spec.ts:13:25) 08:46
Spec Files:	 0 passed, 1 retries, 1 failed, 1 total (100% completed) in 00:08:42 08:46
npm ERR! code ELIFECYCLE 08:46
npm ERR! errno 1 08:46
npm ERR! flowcrypt-appium@1.0.0 only.test.smoke: `wdio ./config/wdio.ios.app.conf.js --suite smoke` 08:46
npm ERR! Exit status 1 08:46
npm ERR! 08:46
npm ERR! Failed at the flowcrypt-appium@1.0.0 only.test.smoke script. 08:46
npm ERR! This is probably not a problem with npm. There is likely additional logging output above. 08:46
  08:47
npm ERR! A complete log of this run can be found in: 08:47
npm ERR!     /Users/semaphore/.npm/_logs/2021-10-25T14_01_35_995Z-debug.log 08:47

[tomholub]

https://flowcrypt.semaphoreci.com/jobs/09404069-963b-4b3f-9489-d5bb23914a9f

[tomholub]

one more here https://flowcrypt.semaphoreci.com/jobs/812ae23e-2137-4fd1-8bdf-051e59c5b0e0 it's a common issue

[fcvakintos]

Testing fix in https://flowcrypt.semaphoreci.com/workflows/1829b6e8-d58c-4374-ba4c-7c62025ea15d?pipeline_id=66ae2181-b5ea-4bd2-ba25-9490144eabf3

[fcvakintos]

Strange issue, appium can't find it. I will try to use another selector for that field, hope it will help

[tomholub]

Strange issue, appium can't find it. I will try to use another selector for that field, hope it will help

You can liberally add accessibility identifiers to our codebase. Then refer to the elements by the accessibility identifier. That's the easiest and most robust.

[dimacnj]

Seems locator will not fix the problem, this problem when we switching from webview to native screens