Fix unstable SemaphoreCI tests

[ioanmo226]

This PR fixed unstable SemaphoreCI tests.

close #2638 // if this PR closes an issue

---

Tests (delete all except exactly one):

• Tests added or updated

---

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

[ioanmo226]

@sosnovsky Have any idea why this test fails (can't click button even though elements are visible on the screen)

[sosnovsky]

Can be caused by some changes in iOS behavior which were adapted in the newer Appium version.
After upgrading to the latest Appium we can re-check if it works there.

[ioanmo226]

@sosnovsky I’ve fixed most of the unstable tests, but in a few cases, they still occasionally fail on SemaphoreCI.

The main issue seems to be a 2-hour timeout limit we set in SemaphoreCI config, where tests get stuck on the home screen (with a list of apps in a closed state) or on the loading progress HUD.
Looks like we need to live with this until SemaphoreCI upgrades to M2 or M3 Macs.

Let me know your thoughts

[sosnovsky]

Looks good, thanks for checking out, hope it'll help to make tests passing in the new PRs 👍

[sosnovsky]

The main issue seems to be a 2-hour timeout limit we set in SemaphoreCI config, where tests get stuck on the home screen (with a list of apps in a closed state) or on the loading progress HUD.
Looks like we need to live with this until SemaphoreCI upgrades to M2 or M3 Macs.

It should be ok for now, as previously it was almost impossible to make all tests pass.
Let's hope Semaphore will start using M3 machines soon, which should greatly improve tests performance.