f7b975ec17
chore: comment out password strength test and other minor updates
2024-02-29 13:23:10 +03:00
7e139e27ae
chore: remove flaky mark from change password test
...
- removed the flaky mark from change password test
- increased timeout for 30 seconds just now (i communicated that to be enough)
We need this test to show actual result , because we missed https://github.com/status-im/status-desktop/issues/13748 because of this
2024-02-28 10:42:40 +03:00
9e22191ecd
chore: fix network namings
2024-02-26 13:03:37 +03:00
b309456a33
chore: combine 2 tests to save time
2024-02-19 11:13:44 +03:00
9b11caf5a2
test: updated permission test with editing and deleting
2024-02-16 14:44:30 +03:00
af5c5a7650
chore: remove change password test from critical path
2024-02-16 10:10:59 +03:00
1fc44f5e3d
chore: replace file dialog interactions with direct function
2024-02-16 10:10:59 +03:00
d339629d59
chore: small changes to wallet settings tests
2024-02-15 10:37:53 +03:00
5d4a6d631d
chore: mark change password test as xfail again
2024-02-12 17:26:20 +03:00
6f84fe7c08
chore: fixes for fails from nightly run
2024-02-12 10:27:31 +03:00
299a702e33
chore: change password test fixed
2024-02-10 19:56:48 +03:00
579cfb4f02
chore: fix for edit status account test
2024-02-08 10:26:12 +03:00
9334508711
chore: align wallet tests with test rail
2024-02-05 07:39:10 +03:00
ace7e27fc3
chore: enabling tests with contact requests
2024-01-31 16:04:14 +03:00
17a3f06e32
chore: disabled tests with contact requests because it's broken
2024-01-30 12:28:02 +07:00
e2f2a34a8b
Increase timeout for wait_for_port
...
Following up Squish advise:
In the wait_for_port.py, you are using socket.create_connection() where the timeout is set to 1.
Could you increase the timeout here and also put a check before to make sure that port is not in the use anymore, before proceeding to launch the AUT.
2024-01-23 10:06:21 +03:00
a9427fc15b
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
e0656e2775
chore: messaging tests enabled back
2024-01-17 17:39:12 +07:00
2a5684a2f7
chore: fix references for test cases in test rail (remove experimental stuff)
2024-01-17 13:22:30 +03:00
a467cbf9f9
chore: test edit network fixed
2024-01-16 15:26:18 +07:00
f2721bc0b1
chore: fixes for saved addresses tests, edit network tests disabled for now
2024-01-16 14:42:27 +07:00
1d09ffba48
chore: reporting test to 2 different test cases in Testrail
2024-01-15 16:07:26 +07:00
c7757a4bee
chore: marked several tests with xfail mark because of bug with contact requests
2024-01-12 15:17:57 +03:00
e45da2c9b6
test: adding test for ability to add saved address from wallet settings
2024-01-11 17:49:36 +03:00
7b1e303156
chore: add multiple references for tests
2024-01-10 18:17:38 +03:00
0cdadf063e
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
fe4325b5e1
chore: introduce timeout mark and update requirements
2023-12-26 19:14:36 +03:00
1d3994f720
chore: add smaller steps and asserts, rename method
2023-12-21 23:10:47 +03:00
ba3626e017
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
8b65d1ca43
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
0edf28f14d
chore: add asserts for change password test
2023-12-18 11:52:57 +03:00
caef79d2ee
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
467f65ac1a
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
b900ee72d6
set up pytest marks for different sections of the app
2023-12-13 17:53:24 +03:00
8fe9b4731c
chore: move the TEST MODE back off for now and add some more fixes
2023-12-13 17:20:30 +03:00
0573a1ea29
chore: fix delete account test according new designs
2023-12-13 17:20:30 +03:00
4f73e0eb52
chore: refactor edit account test a bit
2023-12-13 17:20:30 +03:00
427682f143
chore: skip ENS name test because of bug
...
https://github.com/status-im/status-desktop/issues/12988
2023-12-12 14:29:41 +03:00
d91eae246e
chore: skip balance test because of cryptocompare API limit
...
I logged https://github.com/status-im/status-desktop/issues/12987 which has some details
2023-12-12 14:29:41 +03:00
4f69111778
test: test_ens_name_purchase added
2023-12-12 10:43:20 +07:00
6614475ddc
chore: wait until appears removed
2023-12-11 18:31:08 +03:00
b8202244b3
chore: extend the limit for balance to appear up to 10 seconds
2023-12-08 19:50:19 +03:00
fa48dad825
test: test_wallet_send_0_eth added
2023-12-07 16:24:38 +07:00
2ad53d7599
chore: increase timeout for logout up to 10 seconds
2023-12-07 09:38:47 +03:00
4214103a6a
chore: enable back balance test
2023-12-07 09:38:47 +03:00
ae0b9d4d55
chore: remove unnecessary assert, timeout should do its job
2023-12-05 16:54:29 +03:00
c2ac1db048
chore: add timeout and assert for the sign out test ( #361 )
2023-12-04 18:23:49 +03:00
4500d0fb1d
chore: removed skip mark from syncing and messaging tests, these tests are passing now ( #360 )
2023-12-04 14:18:06 +03:00
eb45281f2d
chore: change Squish version and disable flaky tests ( #359 )
...
* chore: use newer squish
* chore: test tests with squish 7.2.1
2023-12-01 22:04:11 +03:00
Jakub Sokołowski
bbc81717ce
fix(all): refactor killing processes and waiting
...
* Use `psutils.pid_exists()` instead of iterating processes for no reason.
* Drop use of recursion which is completely unnecessarily complex. Use loop.
* Remove checking of `returncode` right away after process starts, it's too soon.
* Lower `PROCESS_TIMEOUT_SEC` to 5 seconds to avoid needless delays.
Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-12-01 14:48:46 +01:00
Anastasiya Semenkevich
Valentina Novgorodtceva
Magnus
Anastasiya
Valentina1133
Jakub Sokołowski