Update trailing spaces

Update UI component mainWindow_Password_textField
This commit is contained in:
femi 2022-07-13 09:29:51 +01:00 committed by Olufemi Ade-Olusile
parent f415e4ae3a
commit 4391d616b6
4 changed files with 158 additions and 158 deletions

View File

@ -17,4 +17,4 @@ def verify_object_enabled(objName: str, timeout: int=_MIN_WAIT_OBJ_TIMEOUT, cond
def verify_text_matching(objName: str, text: str):
test.verify(is_text_matching(objName, text), True)

View File

@ -30,7 +30,7 @@ class SignUpComponents(Enum):
NEW_PASSWORD_BUTTON: str = "mainWindow_New_password_PlaceholderText"
PASSWORD_INPUT: str = "loginView_passwordInput"
CONFIRM_PASSWORD: str = "mainWindow_Confirm_password_PlaceholderText"
PASSWORD_CONFIRM_INPUT: str = "mainWindow_inputValue_StyledTextField"
PASSWORD_CONFIRM_INPUT: str = "mainWindow_Password_textField"
CREATE_PASSWORD: str = "mainWindow_Create_password_StatusBaseText"
CONFIRM_PASSWORD_AGAIN: str = "mainWindow_Confirm_you_password_again_PlaceholderText"
FINALIZE_PASSWORD_STEP: str = "mainWindow_Finalise_Status_Password_Creation_StatusBaseText"

View File

@ -25,7 +25,7 @@ mainWindow_Confirm_password_PlaceholderText = {"container": statusDesktop_mainWi
mainWindow_Display_name_StatusBaseText = {"container": statusDesktop_mainWindow, "text": "Display name", "type": "StatusBaseText", "unnamed": 1, "visible": True}
mainWindow_nextBtn_StatusButton = {"container": statusDesktop_mainWindow, "id": "nextBtn", "type": "StatusButton", "unnamed": 1, "visible": True}
mainWindow_New_password_PlaceholderText = {"container": statusDesktop_mainWindow, "text": "New password", "type": "PlaceholderText", "unnamed": 1, "visible": True}
mainWindow_inputValue_StyledTextField = {"container": statusDesktop_mainWindow, "echoMode": 2, "id": "inputValue", "occurrence": 2, "passwordCharacter": "", "type": "StyledTextField", "unnamed": 1, "visible": True}
mainWindow_Password_textField = {"container": statusDesktop_mainWindow, "echoMode": 2, "id": "inputValue", "occurrence": 2, "passwordCharacter": "", "type": "StyledTextField", "unnamed": 1, "visible": True}
mainWindow_Rectangle = {"container": statusDesktop_mainWindow, "occurrence": 11, "type": "Rectangle", "unnamed": 1, "visible": True}
mainWindow_Create_password_StatusBaseText = {"container": statusDesktop_mainWindow, "text": "Create password", "type": "StatusBaseText", "unnamed": 1, "visible": True}
mainWindow_Confirm_you_password_again_PlaceholderText = {"container": statusDesktop_mainWindow, "text": "Confirm you password (again)", "type": "PlaceholderText", "unnamed": 1, "visible": True}

View File

@ -11,191 +11,191 @@
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.
As a user I want to Sign-up into the Status Desktop application.
The following scenarios cover Sign up process.
Scenario: User signs up and signs in with password
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
Scenario: User signs up and signs in with password
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
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 ui-component mainWindow_edit_TextEdit
Then the following ui-component mainWindow_Next_StatusBaseText is not enabled
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 ui-component mainWindow_edit_TextEdit
Then the following ui-component mainWindow_Next_StatusBaseText is not enabled
Examples:
| username |
| Athl |
| Nervo |
| Gra |
| tester3@ |
Examples:
| username |
| Athl |
| Nervo |
| Gra |
| tester3@ |
Scenario Outline: User cannot sign up with wrong password format
Given A first time user lands on the status desktop and generates new key
When the user inputs username <username>
Scenario Outline: User cannot sign up with wrong password format
Given A first time user lands on the status desktop and generates new key
When the user inputs username <username>
# Input wrong password format in both new password and confirmation input and verify create password button is not enabled
When user inputs the following <wrongpassword> with ui-component loginView_passwordInput
And user inputs the following <wrongpassword> with ui-component mainWindow_inputValue_StyledTextField
Then the following ui-component mainWindow_Create_password_StatusBaseText is not enabled
When user inputs the following <wrongpassword> with ui-component loginView_passwordInput
And user inputs the following <wrongpassword> with ui-component mainWindow_Password_textField
Then the following ui-component mainWindow_Create_password_StatusBaseText is not enabled
# Input right password format in new password input but incorrect in confirmation password input and verify create password button is not enabled
When user inputs the following <password> with ui-component loginView_passwordInput
And user inputs the following <wrongpassword> with ui-component mainWindow_inputValue_StyledTextField
Then the following ui-component mainWindow_Create_password_StatusBaseText is not enabled
When user inputs the following <password> with ui-component loginView_passwordInput
And user inputs the following <wrongpassword> with ui-component mainWindow_Password_textField
Then the following ui-component mainWindow_Create_password_StatusBaseText is not enabled
Examples:
| username | wrongpassword | password |
| tester123 | Invalid34 | TesTEr16843/!@00 |
| tester124 | badP | TesTEr16843/!@01 |
| tester124 | bad2!s | TesTEr16843/!@01 |
Examples:
| username | wrongpassword | password |
| tester123 | Invalid34 | TesTEr16843/!@00 |
| tester124 | badP | TesTEr16843/!@01 |
| tester124 | bad2!s | TesTEr16843/!@01 |
Scenario Outline: User cannot finish Sign Up and Sign In process with wrong password
Given A first time user lands on the status desktop and generates new key
When the user inputs username <username>
Scenario Outline: User cannot finish Sign Up and Sign In process with wrong password
Given A first time user lands on the status desktop and generates new key
When the user inputs username <username>
# Input correct password format in both new password and confirmation input
When user inputs the following <password> with ui-component loginView_passwordInput
And user inputs the following <password> with ui-component mainWindow_inputValue_StyledTextField
And user clicks on the following ui-component mainWindow_Create_password_StatusBaseText
When user inputs the following <password> with ui-component loginView_passwordInput
And user inputs the following <password> with ui-component mainWindow_Password_textField
And user clicks on the following ui-component mainWindow_Create_password_StatusBaseText
# Input wrong password in final password input and verify password creation button is not enabled
When user inputs the following <wrongpassword> with ui-component loginView_passwordInput
Then the following ui-component mainWindow_Finalise_Status_Password_Creation_StatusBaseText is not enabled
When user inputs the following <wrongpassword> with ui-component loginView_passwordInput
Then the following ui-component mainWindow_Finalise_Status_Password_Creation_StatusBaseText is not enabled
Examples:
| username | wrongpassword | password |
| tester123 | Invalid34 | TesTEr16843/!@00 |
| tester123 | TesTEr16843/!@) | TesTEr16843/!@01 |
Examples:
| username | wrongpassword | password |
| tester123 | Invalid34 | TesTEr16843/!@00 |
| tester123 | TesTEr16843/!@) | TesTEr16843/!@01 |
Scenario: User signs up with imported 12 seed phrase
Scenario: User signs up with imported 12 seed phrase
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs 12 seed phrases
| phrases | occurrence |
| lawn | 1 |
| corn | 3 |
| paddle | 5 |
| survey | 7 |
| shrimp | 9 |
| mind | 11 |
| select | 2 |
| gaze | 4 |
| arrest | 6 |
| pear | 8 |
| reduce | 10 |
| scan | 12 |
And user clicks on the following ui-component mainWindow_submitButton_StatusButton
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
And the user activates wallet and opens the wallets section
Then the 12 seed phrase address is 0x8285cb9bf17b23d64a489a8dad29163dd227d0fd displayed in the wallet
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs 12 seed phrases
| phrases | occurrence |
| lawn | 1 |
| corn | 3 |
| paddle | 5 |
| survey | 7 |
| shrimp | 9 |
| mind | 11 |
| select | 2 |
| gaze | 4 |
| arrest | 6 |
| pear | 8 |
| reduce | 10 |
| scan | 12 |
And user clicks on the following ui-component mainWindow_submitButton_StatusButton
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
And the user activates wallet and opens the wallets section
Then the 12 seed phrase address is 0x8285cb9bf17b23d64a489a8dad29163dd227d0fd displayed in the wallet
Scenario: User signs up with imported 18 seed phrase
Scenario: User signs up with imported 18 seed phrase
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs 18 seed phrases
| phrases | occurrence |
| flip | 1 |
| foam | 4 |
| time | 7 |
| sight | 10 |
| scheme | 13 |
| describe | 16 |
| candy | 2 |
| erosion | 5 |
| layer | 8 |
| depth | 11 |
| extend | 14 |
| dish | 17 |
| fog | 3 |
| seven | 6 |
| budget | 9 |
| denial | 12 |
| body | 15 |
| device | 18 |
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs 18 seed phrases
| phrases | occurrence |
| flip | 1 |
| foam | 4 |
| time | 7 |
| sight | 10 |
| scheme | 13 |
| describe | 16 |
| candy | 2 |
| erosion | 5 |
| layer | 8 |
| depth | 11 |
| extend | 14 |
| dish | 17 |
| fog | 3 |
| seven | 6 |
| budget | 9 |
| denial | 12 |
| body | 15 |
| device | 18 |
And user clicks on the following ui-component mainWindow_submitButton_StatusButton
When user signs up with username tester124 and password TesTEr16843/!@00
Then the user lands on the signed in app
When the user opens app settings screen
And the user activates wallet and opens the wallets section
Then the 18 seed phrase address is 0xba1d0d6ef35df8751df5faf55ebd885ad0e877b0 displayed in the wallet
And user clicks on the following ui-component mainWindow_submitButton_StatusButton
When user signs up with username tester124 and password TesTEr16843/!@00
Then the user lands on the signed in app
When the user opens app settings screen
And the user activates wallet and opens the wallets section
Then the 18 seed phrase address is 0xba1d0d6ef35df8751df5faf55ebd885ad0e877b0 displayed in the wallet
Scenario: User signs up with imported 24 seed phrase
Scenario: User signs up with imported 24 seed phrase
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs 24 seed phrases
| phrases | occurrence |
| abstract | 1 |
| maple | 5 |
| license | 9 |
| damage | 13 |
| margin | 17 |
| marine | 21 |
| prevent | 2 |
| neutral | 6 |
| slender | 10 |
| unique | 14 |
| sphere | 18 |
| drama | 22 |
| exact | 3 |
| pottery | 7 |
| just | 11 |
| consider | 15 |
| debate | 19 |
| dial | 23 |
| oil | 4 |
| deny | 8 |
| timber | 12 |
| angle | 16 |
| exhibit | 20 |
| actress | 24 |
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs 24 seed phrases
| phrases | occurrence |
| abstract | 1 |
| maple | 5 |
| license | 9 |
| damage | 13 |
| margin | 17 |
| marine | 21 |
| prevent | 2 |
| neutral | 6 |
| slender | 10 |
| unique | 14 |
| sphere | 18 |
| drama | 22 |
| exact | 3 |
| pottery | 7 |
| just | 11 |
| consider | 15 |
| debate | 19 |
| dial | 23 |
| oil | 4 |
| deny | 8 |
| timber | 12 |
| angle | 16 |
| exhibit | 20 |
| actress | 24 |
And user clicks on the following ui-component mainWindow_submitButton_StatusButton
When user signs up with username tester124 and password TesTEr16843/!@00
Then the user lands on the signed in app
When the user opens app settings screen
And the user activates wallet and opens the wallets section
Then the 24 seed phrase address is 0x28cf6770664821a51984daf5b9fb1b52e6538e4b displayed in the wallet
And user clicks on the following ui-component mainWindow_submitButton_StatusButton
When user signs up with username tester124 and password TesTEr16843/!@00
Then the user lands on the signed in app
When the user opens app settings screen
And the user activates wallet and opens the wallets section
Then the 24 seed phrase address is 0x28cf6770664821a51984daf5b9fb1b52e6538e4b displayed in the wallet
Scenario: User signs up with wrong imported seed phrase
Scenario: User signs up with wrong imported seed phrase
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs 24 seed phrases
| phrases | occurrence |
| abstract | 1 |
| maple | 5 |
| games | 9 |
| damage | 13 |
| margin | 17 |
| drama | 21 |
| prevent | 2 |
| neutral | 6 |
| timber | 10 |
| unique | 14 |
| sphere | 18 |
| only | 22 |
| exact | 3 |
| pottery | 7 |
| just | 11 |
| consider | 15 |
| actress | 19 |
| dial | 23 |
| oil | 4 |
| deny | 8 |
| dial | 12 |
| timber | 16 |
| exhibit | 20 |
| house | 24 |
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs 24 seed phrases
| phrases | occurrence |
| abstract | 1 |
| maple | 5 |
| games | 9 |
| damage | 13 |
| margin | 17 |
| drama | 21 |
| prevent | 2 |
| neutral | 6 |
| timber | 10 |
| unique | 14 |
| sphere | 18 |
| only | 22 |
| exact | 3 |
| pottery | 7 |
| just | 11 |
| consider | 15 |
| actress | 19 |
| dial | 23 |
| oil | 4 |
| deny | 8 |
| dial | 12 |
| timber | 16 |
| exhibit | 20 |
| house | 24 |
Then the following ui-component mainWindow_submitButton_StatusButton is not enabled
Then the following ui-component mainWindow_submitButton_StatusButton is not enabled