status-im
/
status-desktop
mirror of https://github.com/status-im/status-desktop.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

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`.
This commit is contained in:
Noelia 2022-10-19 12:39:48 +02:00 committed by Noelia
parent 728aa00c3c
commit cc64e443e4
16 changed files with 121 additions and 128 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
test/ui-test/testSuites/global_shared/steps/steps.py
View File

@ -27,7 +27,7 @@ _statusChat = StatusChatScreen()
### PRECONDITIONS region:
#########################
@Given("the user starts the application with a specific data folder |any|")
@Given("the user starts the application with a specific data folder \"|any|\"")
def step(context, data_folder_path):
clear_directory(context.userData["status_data_folder_path"])
copy_directory(data_folder_path, context.userData["status_data_folder_path"])
@ -53,7 +53,7 @@ def step(context, text, obj):
def step(context, obj):
click_on_an_object(obj)
@When("the user joins chat room |any|")
@When("the user joins chat room \"|any|\"")
def step(context, room):
when_the_user_joins_chat_room(room)

2
test/ui-test/testSuites/suite_communities/tst_communityFlows/test.feature
View File

@ -17,7 +17,7 @@ Feature: Status Desktop community
Background:
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
When user signs up with username "tester123" and password "TesTEr16843/!@00"
Then the user lands on the signed in app
When the user opens the community portal section
Then the user lands on the community portal section

6
test/ui-test/testSuites/suite_communities/tst_communityMessageFlows/test.feature
View File

@ -16,7 +16,7 @@ Feature: Status Desktop community messages
Background:
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
When user signs up with username "tester123" and password "TesTEr16843/!@00"
Then the user lands on the signed in app
When the user opens the community portal section
Then the user lands on the community portal section
@ -44,10 +44,10 @@ Feature: Status Desktop community messages
Scenario: User pins and unpins messages
# This one wont work until #6554 is fixed
# And the amount of pinned messages is 0
When the user sends the chat message Message 1
When the user sends the chat message "Message 1"
And the user pins the message at index 0
Then the amount of pinned messages is 1
Then user is able to send chat message
Then the user is able to send chat message
| message |
| Hello |
| How are you |

10
test/ui-test/testSuites/suite_communities/tst_searchFlows/test.feature
View File

@ -17,10 +17,10 @@ Feature: Search feature (ctrl+F)
Background:
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
When user signs up with username "tester123" and password "TesTEr16843/!@00"
Then the user lands on the signed in app
When user joins chat room search-automation-test-1
And user joins chat room search-automation-test-2
When the user joins chat room "search-automation-test-1"
And the user joins chat room "search-automation-test-2"
When the user opens the community portal section
Then the user lands on the community portal section
When the user creates a community named myCommunity, with description My community description, intro Community Intro and outro Community Outro
@ -47,7 +47,7 @@ Feature: Search feature (ctrl+F)
@mayfail
Scenario: User can search for a message in a public channel
When the user opens the chat section
And user joins chat room search-automation-test-1
And the user joins chat room "search-automation-test-1"
Then the user is able to send a random chat message
# Go back to the portal so that we see if the search really redirects
When the user opens the community portal section
@ -55,4 +55,4 @@ Feature: Search feature (ctrl+F)
And the user searches the random message
Then the search menu shows 1 results
When the user clicks on the search result for the random message
Then the chat title is search-automation-test-1
Then the chat title is "search-automation-test-1"

47
test/ui-test/testSuites/suite_messaging/shared/steps/chatSteps.py
View File

@ -13,15 +13,15 @@ _statusCreateChatView = StatusCreateChatScreen()
### PRECONDITIONS region:
#########################
@Given("the user sends a chat message |any|")
@Given("the user sends a chat message \"|any|\"")
def step(context, message):
the_user_sends_a_chat_message(message)
@Given("the image |any| is not unfurled in the chat")
@Given("the image \"|any|\" is not unfurled in the chat")
def step(context: any, image_link: str):
_statusChat.verify_image_unfurled_status(image_link, False)
@Given("the user types |any|")
@Given("the user types \"|any|\"")
def step(context, message):
_statusChat.type_message(message)
@ -41,7 +41,7 @@ def step(context):
def step(context):
the_group_chat_is_created()
@Given("the user clicks on |any| chat")
@Given("the user clicks on \"|any|\" chat")
def step(context, chatName):
_statusMain.open_chat(chatName)
@ -49,11 +49,11 @@ def step(context, chatName):
def step(context):
_statusChat.open_group_chat_edit_popup()
@Given("the user changes the group name to |any|")
@Given("the user changes the group name to \"|any|\"")
def step(context, groupName):
_statusChat.group_chat_edit_name(groupName)
@Given("the user changes the group color to |any|")
@Given("the user changes the group color to \"|any|\"")
def step(context, groupColor):
_statusChat.group_chat_edit_color(groupColor)
@ -77,19 +77,19 @@ def step(context):
def step(context):
when_the_user_opens_the_chat_section()
@When("the user sends a chat message |any|")
@When("the user sends a chat message \"|any|\"")
def step(context, message):
the_user_sends_a_chat_message(message)
@When("the user replies to the message at index |any| with |any|")
@When("the user replies to the message at index |any| with \"|any|\"")
def step(context, message_index, message):
_statusChat.reply_to_message_at_index(message_index, message)
@When("the user edits the message at index |any| and changes it to |any|" )
@When("the user edits the message at index |any| and changes it to \"|any|\"" )
def step(context, message_index, message):
_statusChat.edit_message_at_index(message_index, message)
@When("the user marks the channel |any| as read")
@When("the user marks the channel \"|any|\" as read")
def step(context, channel):
_statusMain.mark_as_read(channel)
@ -110,15 +110,15 @@ def step(context):
def step(context):
_statusChat.press_enter()
@When("the user inputs a mention to |any| with message |any|")
@When("the user inputs a mention to \"|any|\" with message \"|any|\"")
def step(context,displayName,message):
_statusChat.send_message_with_mention(displayName, message)
@When("the user sends the emoji |any| as a message")
@When("the user sends the emoji \"|any|\" as a message")
def step(context, emoji_short_name):
_statusChat.send_emoji(emoji_short_name, "")
@When("the user sends the emoji |any| with message |any|")
@When("the user sends the emoji \"|any|\" with message \"|any|\"")
def step(context, emoji_short_name, message):
_statusChat.send_emoji(emoji_short_name, message)
@ -134,7 +134,7 @@ def step(context):
_statusChat.send_message(message)
context.userData["randomMessage"] = message
@When("the user switches to |any| chat")
@When("the user switches to \"|any|\" chat")
def step(context, chatName):
_statusChat.switch_to_chat(chatName)
@ -154,21 +154,21 @@ def step(context):
### VERIFICATIONS region:
#########################
@Then("the last chat message contains |any|")
@Then("the last chat message contains \"|any|\"")
def step(context, message):
_statusChat.verify_last_message_sent(message)
@Then("the chat message |any| is displayed as a reply")
@Then("the chat message \"|any|\" is displayed as a reply")
def step(context, message):
# TODO: Check the last message is really a reply.
_statusChat.verify_last_message_sent(message)
@Then("the chat message |any| is displayed as an edited one")
@Then("the chat message \"|any|\" is displayed as an edited one")
def step(context, message):
# TODO: Check last message is an edited one.
_statusChat.verify_last_message_sent(message)
@Then("the last message displayed is not |any|")
@Then("the last message displayed is not \"|any|\"")
def step(context, message):
_statusChat.verify_last_message_sent_is_not(message)
@ -178,7 +178,6 @@ def step(context):
@Then("the GIF message is displayed")
def step(context):
# TODO: It should be a specific verification call instead of adding here a string (Screen layer responsibility)
_statusChat.verify_last_message_sent("tenor.gif")
@Then("the image |any| is unfurled in the chat")
@ -189,11 +188,11 @@ def step(context: any, image_link: str):
def step(context):
_statusChat.cannot_delete_last_message()
@Then("the |any| mention with message |any| have been sent")
@Then("the \"|any|\" mention with message \"|any|\" have been sent")
def step(context,displayName,message):
_statusChat.verify_last_message_sent_contains_mention(displayName, message)
@Then("the user cannot input a mention to a not existing user |any|")
@Then("the user cannot input a mention to a not existing user \"|any|\"")
def step(context, displayName):
_statusChat.cannot_do_mention(displayName)
@ -217,11 +216,11 @@ def step(context):
def step(context):
the_group_chat_is_created()
@Then("the chat title is |any|")
@Then("the chat title is \"|any|\"")
def step(context, title):
_statusChat.verify_chat_title(title)
@Then("the chat color is |any|")
@Then("the chat color is \"|any|\"")
def step(context, color):
_statusChat.verify_chat_color(color)
@ -229,7 +228,7 @@ def step(context, color):
def step(context):
_statusChat.verify_chat_image(context.userData["fixtures_root"])
@Then("the chat |any| does not exist")
@Then("the chat \"|any|\" does not exist")
def step(context, chatName):
_statusMain.verify_chat_does_not_exist(chatName)

94
test/ui-test/testSuites/suite_messaging/tst_ChatFlow/test.feature
View File

@ -15,8 +15,8 @@ Feature: Status Desktop Chat Basic Flows
# TODO: Add scenario end -> clear chat input.
Scenario Outline: The user can chat in a public room
When the user sends a chat message <message>
Then the last chat message contains <message>
When the user sends a chat message "<message>"
Then the last chat message contains "<message>"
Examples:
| message |
| Hello |
@ -28,56 +28,53 @@ Feature: Status Desktop Chat Basic Flows
@mayfail
# TODO: It works standalone but when it runs as part of the sequence, the action of reply is not done always. The popup option does not appear.
Scenario Outline: The user can reply to the last message
Given the user sends a chat message <message>
When the user replies to the message at index 0 with <reply>
Given the user sends a chat message "random chat message"
When the user replies to the message at index 0 with "<reply>"
# TODO: Check the last message is really a reply, now just checking the last message is the expected one but could not be a reply. The popup option does not appear.
Then the chat message <reply> is displayed as a reply
Then the chat message "<reply>" is displayed as a reply
Examples:
| message | reply |
| random chat message | This is a reply |
| reply |
| This is a reply |
@mayfail
# TODO: It works standalone but when it runs as part of the sequence, the action of edit is not done always. The popup option does not appear.
Scenario Outline: The user can edit a message
Given the user sends a chat message <message>
When the user edits the message at index 0 and changes it to <edited>
Given the user sends a chat message "Edit me"
When the user edits the message at index 0 and changes it to "<edited>"
# TODO: Check last message is an edited one, now just checking the last message is the expected one but could not be an edited one.
Then the chat message <edited> is displayed as an edited one
Then the chat message "<edited>" is displayed as an edited one
Examples:
| message | edited |
| Edit me | Edited by me |
| edited |
| Edited by me |
@relyon-mailserver
Scenario Outline: The user can reply to another message
When the user replies to the message at index 0 with <reply>
Then the chat message <reply> is displayed as a reply
When the user replies to the message at index 0 with "<reply>"
Then the chat message "<reply>" is displayed as a reply
Examples:
| reply |
| This is a reply |
# TODO: This scenario should be extracted to a different feature file bc it doesn't accomplish the background steps since it needs to change/specify the chat room
# Scenario Outline: The user joins a room and marks it as read
# Scenario: The user joins a room and marks it as read
# When the user joins chat room test
# And the user marks the channel <channel> as read
# And the user marks the channel "test" as read
# # TODO find a way to validate that it worked
# Examples:
# | channel |
# | test |
@mayfail
# TODO: It works standalone but when it runs as part of the sequence, the action of delete is not done always. The popup option does not appear.
Scenario Outline: The user can delete his/her own message
Given the user sends a chat message <message>
Given the user sends a chat message "<message>"
When the user deletes the message at index 0
Then the last message displayed is not <message>
Then the last message displayed is not "<message>"
Examples:
| message |
| random chat message |
| message |
| random chat message |
Scenario: The user can clear chat history
Given the user sends a chat message Hi hi
And the user sends a chat message testing chat
And the user sends a chat message history
Given the user sends a chat message "Hi hi"
And the user sends a chat message "testing chat"
And the user sends a chat message "history"
When the user clears chat history
Then the chat is cleared
@ -93,26 +90,23 @@ Feature: Status Desktop Chat Basic Flows
@mayfail
# TODO: It works standalone but when it runs as part of the sequence, the action of activates link preview doesn't work.
Scenario Outline: The user can activate image unfurling
Given the user sends a chat message <image_url>
And the image <image_url> is not unfurled in the chat
Given the user sends a chat message "<image_url>"
And the image "<image_url>" is not unfurled in the chat
When the user opens app settings screen
And the user opens the messaging settings
And the user activates link preview
And the user activates image unfurling
And the user opens the chat section
Then the image <image_url> is unfurled in the chat
Then the image "<image_url>" is unfurled in the chat
Examples:
| image_url |
| https://github.com/status-im/status-desktop/raw/master/test/ui-test/fixtures/images/doggo.jpeg |
Scenario Outline: The user is able to use emoji suggestions
Given the user types <message>
Scenario: The user is able to use emoji suggestions
Given the user types "hello :thumbs"
And the user selects the emoji in the suggestion's list
When the user presses enter
Then the last chat message contains <emoji>
Examples:
| message | emoji |
| hello :thumbs | 👍 |
Then the last chat message contains "👍"
@relyon-mailserver
Scenario: The user cannot delete another user's message
@ -120,28 +114,28 @@ Feature: Status Desktop Chat Basic Flows
@relyon-mailserver
Scenario Outline: The user can do a mention
When the user inputs a mention to <displayName> with message <message>
Then the <displayName> mention with message <message> have been sent
When the user inputs a mention to "<displayName>" with message "<message>"
Then the "<displayName>" mention with message "<message>" have been sent
Examples:
| displayName | message |
| tester123 | testing mention |
@relyon-mailserver
Scenario Outline: The user can not do a mention to a not existing users
Then the user cannot input a mention to a not existing user <displayName>
Then the user cannot input a mention to a not existing user "<displayName>"
Examples:
| displayName |
| notExistingAccount |
| asdfgNoNo |
Scenario: The user can send an emoji as a message
When the user sends the emoji heart_eyes as a message
Then the last chat message contains 😍
When the user sends the emoji "heart_eyes" as a message
Then the last chat message contains "😍"
Scenario Outline: The user can send an emoji in a message
When the user sends the emoji sunglasses with message <message>
Then the last chat message contains 😎
And the last chat message contains <message>
When the user sends the emoji "sunglasses" with message "<message>"
Then the last chat message contains "😎"
And the last chat message contains "<message>"
Examples:
| message |
| wow I'm so cool |
@ -149,14 +143,14 @@ Feature: Status Desktop Chat Basic Flows
# TODO: This scenario should be extracted to a different feature file bc it doesn't accomplish the background steps since it needs to change/specify the chat room
# @merge
# Scenario: The user sees chats sorted by most recent activity
# When the user joins chat room first-chat
# And the user joins chat room second-chat
# And the user joins chat room third-chat
# When the user joins chat room "first-chat"
# And the user joins chat room "second-chat"
# And the user joins chat room "third-chat"
# Then the user chats are sorted accordingly
# | third-chat |
# | second-chat |
# | first-chat |
# When the user switches to second-chat chat
# When the user switches to "second-chat" chat
# And the user sends a random chat message
# Then the random chat message is displayed
# And the user chats are sorted accordingly
@ -165,9 +159,9 @@ Feature: Status Desktop Chat Basic Flows
# | first-chat |
Scenario: The user can type message with emoji autoreplace
When the user sends a chat message Hello :)
Then the last chat message contains 🙂
And the last chat message contains Hello
When the user sends a chat message "Hello :)"
Then the last chat message contains "🙂"
And the last chat message contains "Hello"
Scenario: The user can send a sticker after installing a free pack
Given the user installs the sticker pack at position 4

40
test/ui-test/testSuites/suite_messaging/tst_groupChat/test.feature
View File

@ -6,8 +6,8 @@ Feature: Status Desktop Group Chat
Background:
Given the user starts the application with a specific data folder ../../../fixtures/group_chat
When the user tester123 logs in with password TesTEr16843/!@00
Given the user starts the application with a specific data folder "../../../fixtures/group_chat"
When the user "tester123" logs in with password "TesTEr16843/!@00"
Then the user lands on the signed in app
@relyon-mailserver
@ -22,29 +22,29 @@ Feature: Status Desktop Group Chat
| Athletic |
| Nervous |
When the user sends a chat message <message1>
Then the chat title is Athletic&Nervous
And the last chat message contains <message1>
When the user sends a chat message "<message1>"
Then the chat title is "<groupName>"
And the last chat message contains "<message1>"
# Invited user 1
Given the user restarts the app
And the user Nervous logs in with password TesTEr16843/!@00
And the user "Nervous" logs in with password "TesTEr16843/!@00"
And the user lands on the signed in app
And the user clicks on Athletic&Nervous chat
When the user sends a chat message <message2>
Then the last chat message contains <message2>
And the user clicks on "<groupName>" chat
When the user sends a chat message "<message2>"
Then the last chat message contains "<message2>"
# Invited user 2
Given the user restarts the app
And the user Athletic logs in with password TesTEr16843/!@00
And the user "Athletic" logs in with password "TesTEr16843/!@00"
And the user lands on the signed in app
And the user clicks on Athletic&Nervous chat
When the user sends a chat message <message3>
Then the last chat message contains <message3>
And the user clicks on "<groupName>" chat
When the user sends a chat message "<message3>"
Then the last chat message contains "<message3>"
Examples:
| message1 | message2 | message3 |
| Admin user message sent | Invited user 1 message sent!! | Invited user 2 message sent!! |
| message1 | message2 | message3 | groupName |
| Admin user message sent | Invited user 1 message sent!! | Invited user 2 message sent!! | Athletic&Nervous |
# TODO: Add cleanup scenario. Leave, one by one, the chat
@ -55,14 +55,14 @@ Feature: Status Desktop Group Chat
Then the group chat is created
Given the user opens the edit group chat popup
And the user changes the group name to Fat&Lazy
And the user changes the group name to "Fat&Lazy"
When the user saves changes
Then the chat title is Fat&Lazy
Then the chat title is "Fat&Lazy"
Given the user opens the edit group chat popup
And the user changes the group color to #7CDA00
And the user changes the group color to "#7CDA00"
When the user saves changes
Then the chat color is #7CDA00
Then the chat color is "#7CDA00"
Given the user opens the edit group chat popup
And the user changes the group image
@ -70,4 +70,4 @@ Feature: Status Desktop Group Chat
Then the chat image is changed
When the user leaves current chat
Then the chat Fat&Lazy does not exist
Then the chat "Fat&Lazy" does not exist

4
test/ui-test/testSuites/suite_onboarding/shared/steps/loginSteps.py
View File

@ -5,7 +5,7 @@ _loginScreen = StatusLoginScreen()
#########################
### PRECONDITIONS region:
#########################
@Given("the user |any| logs in with password |any|")
@Given("the user \"|any|\" logs in with password \"|any|\"")
def step(context, username, password):
the_user_any_logs_in_with_password(username, password)
@ -13,7 +13,7 @@ def step(context, username, password):
### ACTIONS region:
#########################
@When("the user |any| logs in with password |any|")
@When("the user \"|any|\" logs in with password \"|any|\"")
def step(context, username, password):
the_user_any_logs_in_with_password(username, password)

2
test/ui-test/testSuites/suite_onboarding/shared/steps/signUpSteps.py
View File

@ -25,7 +25,7 @@ def step(context):
### ACTIONS region:
#########################
@When("user signs up with username |any| and password |any|")
@When("user signs up with username \"|any|\" and password \"|any|\"")
def step(context, username, password):
when_the_user_signs_up(username, password)

8
test/ui-test/testSuites/suite_onboarding/tst_statusLoginPassword/test.feature
View File

@ -17,10 +17,10 @@ Feature: Status Desktop login
Scenario Outline: User tries to login with a valid password
Given A first time user lands on the status desktop and generates new key
When user signs up with username <username> and password <password>
When user signs up with username "<username>" and password "<password>"
Then the user lands on the signed in app
When the user restarts the app
And the user <username> logs in with password <password>
And the user "<username>" logs in with password "<password>"
Then the user lands on the signed in app
Examples:
@ -31,10 +31,10 @@ Feature: Status Desktop login
@merge
Scenario Outline: User tries to login with an invalid password
Given A first time user lands on the status desktop and generates new key
When user signs up with username <username> and password <password>
When user signs up with username "<username>" and password "<password>"
Then the user lands on the signed in app
When the user restarts the app
And the user <username> logs in with password <wrongpassword>
And the user "<username>" logs in with password "<wrongpassword>"
Then the user is NOT able to login to Status Desktop application
Examples:
| username | password | wrongpassword |

6
test/ui-test/testSuites/suite_onboarding/tst_statusSignUp/test.feature
View File

@ -16,7 +16,7 @@ Feature: Status Desktop Sign Up
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
When user signs up with username "tester123" and password "TesTEr16843/!@00"
Then the user lands on the signed in app
@ -122,7 +122,7 @@ Feature: Status Desktop Sign Up
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs the seed phrase <seed>
And user clicks on the following ui-component seedPhraseView_Submit_Button
When user signs up with username tester123 and password TesTEr16843/!@00
When user signs up with username "tester123" and password "TesTEr16843/!@00"
Then the user lands on the signed in app
Examples:
| seed | address |
@ -142,7 +142,7 @@ Feature: Status Desktop Sign Up
@merge
Scenario: After Signing up the Profile state should be online
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
When user signs up with username "tester123" and password "TesTEr16843/!@00"
Then the user is online
@merge

6
test/ui-test/testSuites/suite_settings/tst_languageSettings/test.feature
View File

@ -17,7 +17,7 @@ Feature: Status Language Settings
Background:
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
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 clicks on Language & Currency
@ -28,7 +28,7 @@ Feature: Status Language Settings
And the user selects the language <native>
Then the application displays <native> as the selected language
When the user restarts the app
And the user tester123 logs in with password TesTEr16843/!@00
And the user "tester123" logs in with password "TesTEr16843/!@00"
Then the user lands on the signed in app
When the user opens app settings screen
And the user clicks on Language & Currency
@ -67,7 +67,7 @@ Feature: Status Language Settings
And the user selects the language <native>
Then the application displays <native> as the selected language
When the user restarts the app
And the user tester123 logs in with password TesTEr16843/!@00
And the user "tester123" logs in with password "TesTEr16843/!@00"
Then the user lands on the signed in app
When the user opens app settings screen
And the user clicks on Language & Currency

12
test/ui-test/testSuites/suite_settings/tst_settingsMenu/test.feature
View File

@ -5,7 +5,7 @@ Feature: Status Desktop Settings Menu
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
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
@ -25,30 +25,30 @@ Feature: Status Desktop Settings Menu
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
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
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
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
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
And the user "tester123" logs in with password "NewPassword@12345"
Then the user lands on the signed in app

4
test/ui-test/testSuites/suite_settings/tst_userIdentity/test.feature
View File

@ -4,7 +4,7 @@ Feature: User Identity
Background: Sign up and land
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
When user signs up with username "tester123" and password "TesTEr16843/!@00"
Then the user lands on the signed in app
@mayfail
@ -18,7 +18,7 @@ Feature: User Identity
And the user sets bio to "Hello, I am super tester!"
And the user sets display links to twitter: "twitter_handle", personal site: "status.im", "customLink": "customUrl"
And the user restarts the app
And the user tester123_changed logs in with password TesTEr16843/!@00
And the user "tester123_changed" logs in with password "TesTEr16843/!@00"
Then the user lands on the signed in app
When the user opens app settings screen
And the user opens the profile settings

2
test/ui-test/testSuites/suite_wallet/tst_transaction/test.feature
View File

@ -6,7 +6,7 @@ Feature: Status Desktop Transaction
Given A first time user lands on the status desktop and navigates to import seed phrase
When The user inputs the seed phrase pelican chief sudden oval media rare swamp elephant lawsuit wheat knife initial
And user clicks on the following ui-component seedPhraseView_Submit_Button
When user signs up with username tester123 and password qqqqqqqqqq
When user signs up with username "tester123" and password "qqqqqqqqqq"
Then the user lands on the signed in app
When the user opens app settings screen
And the user activates wallet and opens the wallet settings

2
test/ui-test/testSuites/suite_wallet/tst_wallet/test.feature
View File

@ -4,7 +4,7 @@ Feature: Status Desktop Wallet
Background: Sign up & Enable wallet 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
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
When the user activates wallet and opens the wallet section