status-desktop/test/ui-test/testSuites/suite_settings/tst_mainSettingsSection/test.feature

Feature: Status Desktop Main Settings Section

    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.

    The feature start sequence is the following (setup on its own `bdd_hooks`):
    ** given A first time user lands on the status desktop and generates new key
    ** when user signs up with username "tester123" and password "TesTEr16843/!@00"
    ** and the user lands on the signed in app

    Background: Open settings section
        Given the user opens app settings screen

	# TODO: It must be reformulated or extracted to a different feature file bc preconditions of this feature file also include closing the backup seed phrase indicator at first instance
	# so the validation is not providing relevant information
	# TODO: It is also unstable. Needs to be checked.
    @mayfail
    Scenario: The user can backup seed phrase
        Given the user activates wallet
		And the user opens the wallet settings
        When the user backs up the wallet seed phrase
        Then the backup seed phrase indicator is not displayed

    Scenario: The user can switch state to offline
    	When the users switches state to offline
    	Then the user appears offline

    	Given the user restarts the app
    	And the user "tester123" logs in with password "TesTEr16843/!@00"
    	Then the user appears offline

    Scenario: The user can switch state to online
        When the users switches state to offline
    	And the user restarts the app
    	And the user "tester123" logs in with password "TesTEr16843/!@00"
    	Then the user appears offline

        When the users switches state to online
    	Then the user appears online

    	When the user restarts the app
    	And the user "tester123" logs in with password "TesTEr16843/!@00"
    	Then the user appears online

	Scenario: The user can switch state to automatic
        When the users switches state to automatic
    	Then the user status is automatic

    	When the user restarts the app
    	And the user "tester123" logs in with password "TesTEr16843/!@00"
    	Then the user status is automatic

	Scenario: The user can change the password and login with new password
    	When the user changes the password from TesTEr16843/!@00 to NewPassword@12345
    	And the user restarts the app
    	And the user "tester123" logs in with password "NewPassword@12345"
    	Then the user lands on the signed in app
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			The feature start sequence is the following (setup on its own `bdd_hooks`):
			`** given A first time user lands on the status desktop and generates new key`
			`** when user signs up with username "tester123" and password "TesTEr16843/!@00"`
			`** and the user lands on the signed in app`
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`
			`Given 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			`# TODO: It must be reformulated or extracted to a different feature file bc preconditions of this feature file also include closing the backup seed phrase indicator at first instance`
			`# so the validation is not providing relevant information`
test(suite_settings/tst_mainSettingsSection): Disabled `The user can backup seed phrase` bc it is unstable `The user can backup seed phrase` scenario has been disabled due to its instability. It fails sometimes in the CI so it needs a review. 2022-11-18 13:20:30 +00:00			`# TODO: It is also unstable. Needs to be checked.`
			`@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 backup seed phrase`
			`Given the user activates wallet`
test(suite_wallet): Created `bdd_hook` for each `suite_wallet` test case - Created `bdd_hooks` that contain the sing up steps just only once in the feature start and the needed start steps depending on the test case. - Updated feature files removing sign up steps and given/when/then reorganization. Closes #8026 2022-10-21 07:17:48 +00:00			`And the user opens the wallet settings`
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			`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`

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"`
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`

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"`
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"`
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			`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"`
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): 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`