a24da2d72f
chore: disable tests because of broken contact requests
...
Contact requests are dead again in status.prod fleet
Ticket logged: https://github.com/status-im/status-desktop/issues/13246
2024-01-19 11:08:54 +03:00
d8dd50cc63
chore: fixed join community test
2024-01-17 17:39:12 +07:00
5aaa918740
chore: messaging tests enabled back
2024-01-17 17:39:12 +07:00
f77e8ea01d
chore: fix saved addresses on main wallet screen
2024-01-17 13:22:30 +03:00
6e9365b253
chore: fix references for test cases in test rail (remove experimental stuff)
2024-01-17 13:22:30 +03:00
7589b94501
chore: test edit network fixed
2024-01-16 15:26:18 +07:00
081b34067f
chore: fixes for saved addresses tests, edit network tests disabled for now
2024-01-16 14:42:27 +07:00
00e2c52cc9
test: test clicking category added
2024-01-15 16:07:59 +07:00
6694abeaa8
chore: reporting test to 2 different test cases in Testrail
2024-01-15 16:07:26 +07:00
69daf059ec
chore: replace methods of waiting views with methods of checking elements on these views
...
- 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
2024-01-12 15:54:26 +03:00
0ae5e97ec2
chore: marked several tests with xfail mark because of bug with contact requests
2024-01-12 15:17:57 +03:00
a13d8f19de
chore: test_edit_community_channel fix
2024-01-12 15:17:57 +03:00
ce077e998c
chore: fixes for wallet tests
2024-01-12 15:17:57 +03:00
ff3a0e0957
test: adding test for ability to add saved address from wallet settings
2024-01-11 17:49:36 +03:00
d6a2f31980
chore: add multiple references for tests
2024-01-10 18:17:38 +03:00
980b338dac
chore: remove change password test from critical suite
...
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
2024-01-10 11:56:50 +03:00
e12ef344ed
chore: fix saved addresses test according to new designs
2024-01-10 10:39:54 +03:00
da59269a89
chore: toast messages verifications
2024-01-10 10:39:54 +03:00
8c02b7bbd7
chore: update error message
...
Error message has been changed in ff9062a1b0 (diff-4ac30c280b7ceca7b505ab0551b9e009295aae3147253c43ae8821e9d6c0ed69R682)
2024-01-09 16:03:31 +03:00
f664fd4307
chore: combine tests for community screens to reduce total run time
2023-12-29 17:48:03 +03:00
88c823e360
chore: add another verification which will take a bit of time so the UI wont be frozen
2023-12-29 16:42:34 +03:00
4b8d199dab
chore: fix test for creating permissions
2023-12-29 11:47:48 +03:00
07b151dfe9
test: member role tests added
2023-12-28 15:37:02 +03:00
acc3d2286b
test: edit_community_category
2023-12-28 13:58:52 +03:00
4dace0093d
chore: fix join community test according changes in UI
2023-12-28 13:58:22 +03:00
9fc3e8ed6d
chore: change locator for InsertDetailsView
2023-12-27 17:42:34 +03:00
a48fd2e0ea
chore: add timeout for group chat
2023-12-27 11:44:01 +03:00
3aef4930ff
chore: introduce timeout mark and update requirements
2023-12-26 19:14:36 +03:00
7fbcbde117
ci: remove debug
2023-12-25 13:07:09 +01:00
61b73b3251
chore: replace is_visible
2023-12-23 11:02:58 +03:00
41e634fa85
ci: set TEST_SCOPE_FLAG conditionally on JOB_NAME
2023-12-22 20:39:02 +03:00
bbd0e5342f
chore: fix syncing test and move it to critical suite
2023-12-22 19:13:41 +03:00
9181bce340
chore: replace waitFor with waitForObjectExists
...
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
2023-12-22 16:52:55 +03:00
dc7d578e43
chore: add validation for emoji hash across screens
2023-12-21 23:10:47 +03:00
e5b34242d1
chore: better init for online identifier
2023-12-21 23:10:47 +03:00
a6590dfd21
chore: add verification for identicon ring on the profile screen
2023-12-21 23:10:47 +03:00
2b3c7fb698
chore: added random selection of pictures (diff types)
2023-12-21 23:10:47 +03:00
d38979e26e
chore: add randomisation for password
2023-12-21 23:10:47 +03:00
effd82ec17
chore: add randomisation for display name generation
2023-12-21 23:10:47 +03:00
9023f27fbd
chore: add smaller steps and asserts, rename method
2023-12-21 23:10:47 +03:00
21f30f2ee6
chore: update marks and readMe file
...
Fixes https://github.com/status-im/desktop-qa-automation/issues/391
1. replaced all the skip marks for tests that are linked to status-desktop tickets to xfail
2. updated readme to explain marks
2023-12-20 17:38:27 +03:00
230767ef6a
chore: raise exceptions when needed
2023-12-20 15:46:15 +03:00
d8b4492a28
chore: disable join community test until it is fixed
2023-12-19 14:24:50 +03:00
863deed451
ci: run critical tests by default
2023-12-18 16:22:27 +03:00
c38bc86476
chore: mark password change test as flaky
...
Reason: https://github.com/status-im/status-desktop/issues/13013
2023-12-18 11:52:57 +03:00
13146aa80e
chore: add asserts for change password test
2023-12-18 11:52:57 +03:00
0896e395d4
chore: select tests to run against PRs
...
Selected a few to run by critical mark in PRs
2023-12-18 11:52:57 +03:00
663396a10b
chore: introduce flaky mark
...
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.
2023-12-15 16:07:13 +03:00
d8d3cc1235
chore: update readme
2023-12-14 10:45:45 +03:00
2350193548
Add priority pytest marks
2023-12-13 17:53:24 +03:00
Anastasiya Semenkevich
Valentina Novgorodtceva
Anton Iakimov
Magnus