For the difference adding saved addresses providing ens name now waits for an address
associated to that ens to be resolved. And also when adding saved address using an address
we're checking if there is an ens name associated with it.
All that works in local just fine, but on CI fails. Could be due to internet connection loss.
Till we figure out why it's like that, disabling that case.
- added verify_account_popup_present() function
- added verify_profile_view_present() function
- added verify_emojihash_view_present()
Mostly done as an attempt to fix flaky navigation in new keys test. (see https://ci.status.im/job/status-desktop/job/e2e/job/prs/1136/allure/#suites/c48b221cdcfecf89e1eb75d0b8e79672/f41783642f763391/)
So the test clicks Next button twice and then thinks he is already on next screen when it is not. So i added a verification for Profile and Emoji screens that when we returning these views, we first check screen titles and if they are correct - then proceed further
Same function is added for Add Account popup earlier, i forgot to add a call for it
Uncomment the test of adding watch only address, related issue seems to be fixed
Remove `@pytest.critical` mark from `test_settings_profile_change_password.py`. The test is timing out very often now (addressed in https://github.com/status-im/status-desktop/issues/13013)
This test will be still executed in nightly runs
There is a problem with is_visible method now, it is not raising any assertions in case it did not find any object, therefore i suspect it as a potential endless loop (always returns True it seems). I will try to fix that, however it is being used across all the framework so it takes time.
The main idea here is to get rid of endless loop and 15 minutes if waiting for nothing in this certain test
A “flaky” test is a test that usually pass but sometimes it fails.
If a flaky test pass it will be reported normally as test succeed. If the test fails, instead of being reported as failure it will be reported as a xfail.
