status-im
/
status-desktop
mirror of https://github.com/status-im/status-desktop.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

chore: general updates

This commit is contained in:
Anastasiya Semenkevich 2024-03-01 11:29:01 +03:00 committed by Anastasiya
parent 206e3da026
commit 53f0fd1fa0
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
test/e2e/gui/components/change_password_popup.py
View File

@ -17,10 +17,11 @@ class ChangePasswordPopup(BasePopup):
def click_re_encrypt_data_restart_button(self):
"""
Timeout is set as rough estimation of 20 seconds. What is happening when changing password is
Timeout is set as rough estimation of 30 seconds. What is happening when changing password is
the process of re-hashing DB initiated. Taking into account the user is new , so DB is relatively small
I assume, 20 seconds should be enough to finish re-hashing and show the Restart button
I assume, 30 seconds should be enough to finish re-hashing and show the Restart button
This time is not really predictable, especially for huge DBs.
In case it does not please check https://github.com/status-im/status-desktop/issues/13013 for context
"""
self._re_encrypt_data_restart_button.click()
assert driver.waitForObject(self._re_encryption_complete_element.real_name, 30000), \

1
test/e2e/tests/onboarding/test_onboarding_generate_new_keys.py
View File

@ -32,7 +32,6 @@ def keys_screen(main_window) -> KeysView:
@allure.testcase('https://ethstatus.testrail.net/index.php?/cases/view/703010', 'Settings - Sign out & Quit')
@pytest.mark.case(703421, 703010)
@pytest.mark.critical
@pytest.mark.flaky
# reason='https://github.com/status-im/status-desktop/issues/13013'
@pytest.mark.parametrize('user_name, password, user_image, zoom, shift', [
pytest.param(