status-im
/
status-desktop
mirror of https://github.com/status-im/status-desktop.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-desktop/test/ui-test/testSuites/suite_settings/tst_mainSettingsSection/test.feature

60 lines
2.3 KiB
Gherkin
Raw Normal View History

test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
Feature: Status Desktop Main Settings Section
test(@desktop/general): can quit app by going to settings -> quit Fixes: #6905
2022-08-10 10:57:21 +00:00
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
As a user I want to login the app go to Settings and make basic settings actions like change my online state and/or store my seed phrase.
test(@desktop/general): can quit app by going to settings -> quit Fixes: #6905
2022-08-10 10:57:21 +00:00
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
Background: Open settings section
test(suite_settings): fix tests (#10265) #9284
2023-05-03 16:23:12 +00:00
Given A first time user lands on the status desktop and generates new key
And the user signs up with username "tester123" and password "TesTEr16843/!@00"
And the user lands on the signed in app
And the user opens app settings screen
tests(Settings): Can backup seed phrase Added debug helpers found useful in debugging while implementing squish tests Closes: #6902
2022-08-16 16:35:10 +00:00
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
Scenario: The user can backup seed phrase
When the user backs up the wallet seed phrase
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
Then the backup seed phrase indicator is not displayed
test(suite_settings/tst_mainSettingsSection): Fix test on backup seed phrase (#10204) #8279
2023-04-13 14:53:50 +00:00
And the Secure Your Seed Phrase Banner is not displayed
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
test/start multiple app instances added (#10779) * test/start multiple app instances added #10401 * test/Tests on switch user state skipped #10401
2023-05-30 10:24:04 +00:00
@mayfail
fix(@desktop/wallet): Added squish test for change password and relogin fixes #6900
2022-08-24 09:51:20 +00:00
Scenario: The user can switch state to offline
When the users switches state to offline
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
Then the user appears offline
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
Given the user restarts the app
test(chore/style): Applied parameters style consistency on `suite_messaging` and some `onboarding / login` statements To make the feature files style consistent for direct string and also use it for examples (params), it has been introduced "" to all plain strings and also into the parameters, that now will be written like this: "<example-param>": Applied on the complete `suite_messaging` and in specific statements of the `onboarding / login`.
2022-10-19 10:39:48 +00:00
And the user "tester123" logs in with password "TesTEr16843/!@00"
test(suite_settings): fix tests (#10265) #9284
2023-05-03 16:23:12 +00:00
Then the user lands on the signed in app
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
Then the user appears offline
test/start multiple app instances added (#10779) * test/start multiple app instances added #10401 * test/Tests on switch user state skipped #10401
2023-05-30 10:24:04 +00:00
@mayfail
fix(@desktop/wallet): Added squish test for change password and relogin fixes #6900
2022-08-24 09:51:20 +00:00
Scenario: The user can switch state to online
When the users switches state to offline
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
And the user restarts the app
test(chore/style): Applied parameters style consistency on `suite_messaging` and some `onboarding / login` statements To make the feature files style consistent for direct string and also use it for examples (params), it has been introduced "" to all plain strings and also into the parameters, that now will be written like this: "<example-param>": Applied on the complete `suite_messaging` and in specific statements of the `onboarding / login`.
2022-10-19 10:39:48 +00:00
And the user "tester123" logs in with password "TesTEr16843/!@00"
test(suite_settings): fix tests (#10265) #9284
2023-05-03 16:23:12 +00:00
Then the user lands on the signed in app
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
Then the user appears offline
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
fix(@desktop/wallet): Added squish test for change password and relogin fixes #6900
2022-08-24 09:51:20 +00:00
When the users switches state to online
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
Then the user appears online
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
When the user restarts the app
test(chore/style): Applied parameters style consistency on `suite_messaging` and some `onboarding / login` statements To make the feature files style consistent for direct string and also use it for examples (params), it has been introduced "" to all plain strings and also into the parameters, that now will be written like this: "<example-param>": Applied on the complete `suite_messaging` and in specific statements of the `onboarding / login`.
2022-10-19 10:39:48 +00:00
And the user "tester123" logs in with password "TesTEr16843/!@00"
test(suite_settings): fix tests (#10265) #9284
2023-05-03 16:23:12 +00:00
Then the user lands on the signed in app
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
Then the user appears online
test/start multiple app instances added (#10779) * test/start multiple app instances added #10401 * test/Tests on switch user state skipped #10401
2023-05-30 10:24:04 +00:00
@mayfail
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
Scenario: The user can switch state to automatic
fix(@desktop/wallet): Added squish test for change password and relogin fixes #6900
2022-08-24 09:51:20 +00:00
When the users switches state to automatic
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
Then the user status is automatic
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
When the user restarts the app
test(chore/style): Applied parameters style consistency on `suite_messaging` and some `onboarding / login` statements To make the feature files style consistent for direct string and also use it for examples (params), it has been introduced "" to all plain strings and also into the parameters, that now will be written like this: "<example-param>": Applied on the complete `suite_messaging` and in specific statements of the `onboarding / login`.
2022-10-19 10:39:48 +00:00
And the user "tester123" logs in with password "TesTEr16843/!@00"
test(suite_settings): fix tests (#10265) #9284
2023-05-03 16:23:12 +00:00
Then the user lands on the signed in app
fix(@desktop/wallet): Added squish test for the user being able to turn his state to online and/or offline fixes #6895
2022-08-12 16:31:39 +00:00
Then the user status is automatic
tests: Can change own display name in ProfilePopup
2022-08-29 18:03:50 +00:00
test(suite_settings): fix tests (#10265) #9284
2023-05-03 16:23:12 +00:00
# https://github.com/status-im/status-desktop/issues/10287
test: Skip broken/unstable tests Tagged with `@mayfail` some scenarios that seem to be unstable / broken on CI and also locally.
2023-01-24 15:01:14 +00:00
@mayfail
test(suite_settings): Updated bdd hooks and suite reorganization - Created new test case `tst_signUpAndQuit`. - Renamed `tst_settingsMenu` to `tst_mainSettingsSection`. - Created specific `bdd_hooks.py` for test case `tst_mainSettingsSection` and `tst_userIdentity`. Closes #8011
2022-11-16 12:06:37 +00:00
Scenario: The user can change the password and login with new password
fix(@desktop/wallet): Added squish test for change password and relogin fixes #6900
2022-08-24 09:51:20 +00:00
When the user changes the password from TesTEr16843/!@00 to NewPassword@12345
And the user restarts the app
test(chore/style): Applied parameters style consistency on `suite_messaging` and some `onboarding / login` statements To make the feature files style consistent for direct string and also use it for examples (params), it has been introduced "" to all plain strings and also into the parameters, that now will be written like this: "<example-param>": Applied on the complete `suite_messaging` and in specific statements of the `onboarding / login`.
2022-10-19 10:39:48 +00:00
And the user "tester123" logs in with password "NewPassword@12345"
fix(@desktop/wallet): Added squish test for change password and relogin fixes #6900
2022-08-24 09:51:20 +00:00
Then the user lands on the signed in app