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

Feature: Status Desktop Settings Menu

    As a user I want to login the app go to Settings and go through all settings menu
    checking the result of each menu item

    Background: Sign up and open settings section
        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"
        Then the user lands on the signed in app
        When the user opens app settings screen

	@merge @mayfail
    Scenario: The user quits the app
        When the user clicks on Sign out and Quit
        Then the app is closed

	@merge @mayfail
    Scenario: User can backup seed phrase
        When the user activates wallet 
		And the user opens the wallet settings
        And the user backs up the wallet seed phrase
        Then the backup seed phrase indicator is not displayed

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

	@merge
    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(@desktop/general): can quit app by going to settings -> quit Fixes: #6905 2022-08-10 10:57:21 +00:00			`Feature: Status Desktop Settings Menu`

			`As a user I want to login the app go to Settings and go through all settings menu`
			`checking the result of each menu item`

			`Background: Sign up and open settings section`
			`Given A first time user lands on the status desktop and generates new key`
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			`When user signs up with username "tester123" and password "TesTEr16843/!@00"`
test(@desktop/general): can quit app by going to settings -> quit Fixes: #6905 2022-08-10 10:57:21 +00:00			`Then the user lands on the signed in app`
			`When the user opens app settings screen`

test: add merge tag + add missing mayfail 2022-09-20 12:22:04 +00:00			`@merge @mayfail`
test(@desktop/general): can quit app by going to settings -> quit Fixes: #6905 2022-08-10 10:57:21 +00:00			`Scenario: The user quits the app`
			`When the user clicks on Sign out and Quit`
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			`Then the app is closed`

test: add merge tag + add missing mayfail 2022-09-20 12:22:04 +00:00			`@merge @mayfail`
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			`Scenario: User can backup seed phrase`
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			`When the user activates wallet`
			`And the user opens the wallet settings`
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			`And 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: add merge tag + add missing mayfail 2022-09-20 12:22:04 +00:00			`@merge`
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`
			`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 offline`

test: add merge tag + add missing mayfail 2022-09-20 12:22:04 +00:00			`@merge`
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`
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`
			`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`

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