issue 518 appium semaphoreci

[tomholub]

This PR runs Appium tests on semaphoreCI.

close #518

still todo: build the app for running in the CI.

---

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

• addresses the issue it closes (if any)
• code is readable and understandable
• is accompanied with tests, or tests are not needed
• is free of vulnerabilities
• is documented clearly and usefully, or doesn't need documentation

[tomholub]

@fcvakintos I've simplified it so that it's just a single build step for both regular tests and Appium tests.

The longest wait at the moment is to get it built anyway, so the fastlane do_everything step will be probably a pre-reqisite for appium tests anyway.

Fails smoke tests now with:

�[35m[XCUITest]�[39m Error: The application at '/Users/semaphore/git/flowcrypt-ios/appium/apps/FlowCrypt.app' does not exist or is not accessible
�[35m[XCUITest]�[39m     at /Users/semaphore/.nvm/versions/node/v12.22.7/lib/node_modules/appium/node_modules/appium-base-driver/lib/basedriver/helpers.js:234:13
�[35m[XCUITest]�[39m {}

The rest is up to you, not my area. If you need help, ask @sosnovsky or @Kharchevskyi for help. How do you build the app for testing today? Do you use the IDE for that? You'll need to replicate that, but with shell commands. Once you can do it locally, update the semaphore commands to use the same steps, and that will make it work.

[fcvakintos]

@tomholub I was at the same point is to get this app file for testing, I will check tomorrow

[fcvakintos]

@tomholub first success build https://flowcrypt.semaphoreci.com/jobs/02452c1d-9a06-4009-b6bd-d1b3d0daab62, I will optimise building app tomorrow

[tomholub]

excellent

[tomholub]

This is interesting:

Given it's two build steps in sequence, and given both build the same thing (same app), shouldn't the second build step just take 30 seconds? Does it not cache/reuse build data?

[fcvakintos]

hi @RomanKovalchuk2019 @ivan-ushakov please suggest if possible to improve performance of the build. Right now we have step with 2 fastlanes (do_everything and build_e2e). Maybe it's possible to cmbine them or use some option so on second building it will be faster?

[fcvakintos]

after build_e2e we are executing appium tests

[tomholub]

@sosnovsky is the Roman you wanted to tag :-) alternatively @Kharchevskyi may know.

[tomholub]

Looks good - will merge. Will file issues after that.

[tomholub]

Should run all UI tests here, not just smoke, even if it's slow. At least it will force us to optimize / parallelize, in case. I'll file another issue.