2022-05-24 09:58:04 +00:00
|
|
|
#******************************************************************************
|
|
|
|
# Status.im
|
|
|
|
#*****************************************************************************/
|
|
|
|
#/**
|
|
|
|
# * \file test.feature
|
|
|
|
# *
|
|
|
|
# * \test Status Sign up
|
|
|
|
# * \date May 2022
|
|
|
|
# **
|
|
|
|
# *****************************************************************************/
|
|
|
|
|
|
|
|
Feature: Status Desktop Sign Up
|
|
|
|
|
|
|
|
As a user I want to Sign-up into the Status Desktop application.
|
|
|
|
|
|
|
|
The following scenarios cover Sign up process.
|
|
|
|
|
2022-05-26 15:00:00 +00:00
|
|
|
Scenario: User signs up and signs in with password
|
2022-05-24 09:58:04 +00:00
|
|
|
|
|
|
|
Given A first time user lands on the status desktop and generates new key
|
|
|
|
When user inputs username tester123 and password TesTEr16843/!@00
|
|
|
|
Then the user lands on the signed in app
|
|
|
|
|
2022-05-26 15:00:00 +00:00
|
|
|
|
|
|
|
Scenario Outline: User cannot sign up with wrong username format
|
|
|
|
|
|
|
|
Given A first time user lands on the status desktop and generates new key
|
|
|
|
When user inputs the following <username> with object locator mainWindow_edit_TextEdit
|
|
|
|
Then the following object locator mainWindow_Next_StatusBaseText is not enabled
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
| username |
|
|
|
|
| Athl |
|
|
|
|
| Nervo |
|
|
|
|
| Gra |
|
|
|
|
|tester3@ |
|
|
|
|
|
|
|
|
|