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_onboarding/tst_statusLoginPassword/test.feature

44 lines
1.8 KiB
Gherkin
Raw Normal View History

feat(@DesktopApp): SignUp Scenario (Squish Test) Ticket: https://github.com/status-im/status-desktop/issues/5718 Include script to erase data file before each test
2022-05-26 15:00:00 +00:00
#******************************************************************************
# Status.im
#*****************************************************************************/
#/**
# * \file test.feature
# *
# * \test Status Desktop - Login
# * \date February 2022
# **
# *****************************************************************************/
Feature: Status Desktop login
As a user I want to login into the Status Desktop application.
The following scenarios cover login by using a password.
Scenario Outline: User tries to login with a valid password
test(all): fix all remaining tests and comments the broken ones Fixes #6853
2022-08-05 19:52:34 +00:00
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 "<username>" and password "<password>"
test(all): fix all remaining tests and comments the broken ones Fixes #6853
2022-08-05 19:52:34 +00:00
Then the user lands on the signed in app
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 "<username>" logs in with password "<password>"
test(all): fix all remaining tests and comments the broken ones Fixes #6853
2022-08-05 19:52:34 +00:00
Then the user lands on the signed in app
Examples:
test(CreateGroupChat): Create Group Chat - Created new test case with basic create group chat scenario. - Added specific data folder for `tst_groupChat`. - Removed deprecated data folder. - Added dynamic login (depending on the account). - Added global account information in `suite_status/data` folder. - Added new group chat validations, title, history texts, members added and send chat message. - Replaced some ids by objectNames. - Some improvements in `names.py`. - Onboarding objects refactor. Fixes #6444
2022-07-20 12:14:50 +00:00
| username | password |
feat(@DesktopApp): SignUp Scenario (Squish Test) Ticket: https://github.com/status-im/status-desktop/issues/5718 Include script to erase data file before each test
2022-05-26 15:00:00 +00:00
| Athletic_Prime | TesTEr16843/!@00 |
test: add merge tag + add missing mayfail
2022-09-20 12:22:04 +00:00
@merge
feat(@DesktopApp): SignUp Scenario (Squish Test) Ticket: https://github.com/status-im/status-desktop/issues/5718 Include script to erase data file before each test
2022-06-01 02:43:53 +00:00
Scenario Outline: User tries to login with an invalid password
test(all): fix all remaining tests and comments the broken ones Fixes #6853
2022-08-05 19:52:34 +00:00
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 "<username>" and password "<password>"
test(all): fix all remaining tests and comments the broken ones Fixes #6853
2022-08-05 19:52:34 +00:00
Then the user lands on the signed in app
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 "<username>" logs in with password "<wrongpassword>"
test(all): fix all remaining tests and comments the broken ones Fixes #6853
2022-08-05 19:52:34 +00:00
Then the user is NOT able to login to Status Desktop application
Examples:
| username | password | wrongpassword |
| Athletic_Prime | TesTEr16843/!@00 | Invalid34 |
| Granular_Diligent | TesTEr16843/!@11 | Testpwd |
| Nervous_Pesky | TesTEr16843/!@22 | WrongPSW |