issues 739 735 772 run all appium tests, fix changing login lang#771
issues 739 735 772 run all appium tests, fix changing login lang#771
Conversation
disabled 2 specs renamed checkErrorMessage to checkWrongPassPhraseErrorMessage
|
Why is it that tests that restart app don't work - is there something we can do? |
|
@tomholub I need to investigate more... strange thing |
|
@tomholub bundle is changed? |
|
If you mean dependencies, sure - we update them when new versions come. |
|
I think retrying tests once when they fail is good, I would not be disabling that retry setting. But we should still investigate individual retries and improve them. |
I see bundle id with the new version is com.flowcrypt.as.ios.consumer |
I see what you mean now. Yes, that was me, but this change was not intentional for CI tests. CI tests are running the |
please add to env file on semaphoreci |
|
@tomholub let me know when env file updated so I will push all fixes |
|
Interestingly, when I have a look at CI (the regular Swift tests) I see: That would explain why we had to build twice. But now I'm not entirely sure which bundle id is it running for appium. I'll take a closer look. |
|
I've merged master - npm commands were renamed |
|
instead of |
|
@tomholub did you update ENV file to include bundle id for tests? BUNDLE_ID=com.flowcrypt.as.ios.debug add this to env file on semaphore ci |
|
or can I upload myself? |
|
done |
Please wait a bit - I'm cleaning up configurations and bundles, it's a mess. Once done, I'll let you know. I want to make sure it's all orderly. May take an hour or two (before I push / check tests still work / merge it). Then I'll add the updated .env file. |
|
@tomholub pull latest changes, I have all green. But make sure you have correct bundle_id in env file |
| clickMenuIcon () { | ||
| this.menuIcon.waitForDisplayed(); | ||
| this.menuIcon.click(); | ||
| } |
There was a problem hiding this comment.
On browser extension (puppeteer) I use methods like waitAndClick and waitAndType and waitAndRead and so on. Generally, for every element that you interact with, you have to wait until it's there (and anyway it doesn't hurt to make sure first) so I recommend to use such methods (nearly) everywhere.
There was a problem hiding this comment.
yeah, let's make separate task for this to add ActionHelper file
|
@tomholub I added ENV file with specific bundle id but it could be another bundle id and tests will fail. Ah I uploaded wrong file |
|
I'll update the env file from here |
|
updated, re-running. Let's see. Locally they run well now. |
|
@tomholub great progress so far =) job finished w/o any fails even w/o rerun |
#739 - run all tests
#735 - rename method
#772 - failed to change language during login