From 8c12029e46975a98d0bf4d10a1fb2d3e72654391 Mon Sep 17 00:00:00 2001 From: Anthony Laibe Date: Tue, 20 Sep 2022 14:22:04 +0200 Subject: [PATCH] test: add merge tag + add missing mayfail --- ci/Jenkinsfile.uitests | 6 +-- .../tst_passwordStrength/test.feature | 1 + .../tst_statusSignUp/test.feature | 10 ++++ .../suite_status/tst_ChatFlow/test.feature | 28 ++++++---- .../tst_communityFlows/test.feature | 10 +++- .../tst_communityMessageFlows/test.feature | 5 +- .../suite_status/tst_groupChat/test.feature | 1 + .../tst_languageSettings/test.feature | 15 +++--- .../suite_status/tst_searchFlows/test.feature | 3 ++ .../tst_settingsMenu/test.feature | 4 ++ .../tst_statusLoginPassword/test.feature | 3 +- .../suite_status/tst_transaction/test.feature | 49 ++++++++--------- .../tst_userIdentity/test.feature | 2 + .../suite_status/tst_wallet/config.xml | 10 ++++ .../suite_status/tst_wallet/test.feature | 53 +++++-------------- 15 files changed, 114 insertions(+), 86 deletions(-) create mode 100644 test/ui-test/testSuites/suite_status/tst_wallet/config.xml diff --git a/ci/Jenkinsfile.uitests b/ci/Jenkinsfile.uitests index 0b8d58455f..5ba0e0540b 100644 --- a/ci/Jenkinsfile.uitests +++ b/ci/Jenkinsfile.uitests @@ -74,11 +74,11 @@ pipeline { stage('Tests') { steps { script { - def goerli_rpc_port = 8577 + def goerli_rpc_port = 855 + env.EXECUTOR_NUMBER def mnemonic = "pelican chief sudden oval media rare swamp elephant lawsuit wheat knife initial" def goerli_db_path = "$WORKSPACE/test/ui-test/fixtures/ganache-dbs/goerli" docker.image('trufflesuite/ganache:v7.4.1').withRun( - "-p 127.0.0.1:8577:8545 -v ${goerli_db_path}:/goerli-db", + "-p 127.0.0.1:${goerli_rpc_port}:8545 -v ${goerli_db_path}:/goerli-db", "-e 10 -m='${mnemonic}' --chain.chainId 5 --database.dbPath /goerli-db" ) { c -> sh "docker logs ${c.id}" @@ -96,7 +96,7 @@ pipeline { 2 --tags - ~mayfail + ~mayfail,~merge --config addAUT diff --git a/test/ui-test/testSuites/suite_onboarding/tst_passwordStrength/test.feature b/test/ui-test/testSuites/suite_onboarding/tst_passwordStrength/test.feature index 2052879d00..dc97ae3f2a 100644 --- a/test/ui-test/testSuites/suite_onboarding/tst_passwordStrength/test.feature +++ b/test/ui-test/testSuites/suite_onboarding/tst_passwordStrength/test.feature @@ -10,6 +10,7 @@ # *****************************************************************************/ Feature: Password strength validation including UI pixel-perfect validation + @merge Scenario Outline: As a user I want to see the strength of the password Given A first time user lands on the status desktop and generates new key diff --git a/test/ui-test/testSuites/suite_onboarding/tst_statusSignUp/test.feature b/test/ui-test/testSuites/suite_onboarding/tst_statusSignUp/test.feature index 563d3f787b..d0f3f2a8fd 100644 --- a/test/ui-test/testSuites/suite_onboarding/tst_statusSignUp/test.feature +++ b/test/ui-test/testSuites/suite_onboarding/tst_statusSignUp/test.feature @@ -20,6 +20,7 @@ Feature: Status Desktop Sign Up Then the user lands on the signed in app + @merge 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 with ui-component onboarding_DiplayName_Input @@ -32,6 +33,7 @@ Feature: Status Desktop Sign Up | tester3@ | + @merge Scenario Outline: User cannot sign up with wrong password format in both new password and confirmation input Given A first time user lands on the status desktop and generates new key When the user inputs username @@ -46,6 +48,7 @@ Feature: Status Desktop Sign Up | tester124 | bad2!s | + @merge Scenario Outline: User cannot sign up with right password format in new password input but incorrect in confirmation password input Given A first time user lands on the status desktop and generates new key When the user inputs username @@ -59,6 +62,7 @@ Feature: Status Desktop Sign Up | tester124 | badP | TesTEr16843/!@01 | | tester124 | bad2!s | TesTEr16843/!@01 | + @merge Scenario Outline: User cannot sign up with incorrect confirmation-again password Given A first time user lands on the status desktop and generates new key When the user inputs username @@ -73,6 +77,7 @@ Feature: Status Desktop Sign Up | tester123 | Invalid34 | TesTEr16843/!@00 | | tester123 | TesTEr16843/!@) | TesTEr16843/!@01 | + @merge Scenario Outline: User cannot finish Sign Up and Sign In process with wrong password format in both new password and confirmation input Given A first time user lands on the status desktop and generates new key When the user inputs username @@ -84,6 +89,7 @@ Feature: Status Desktop Sign Up | username | wrongpassword | | tester123 | Invalid34 | + @merge Scenario Outline: User cannot finish Sign Up and Sign In process with right password format in new password input but incorrect in confirmation password input Given A first time user lands on the status desktop and generates new key When the user inputs username @@ -96,6 +102,7 @@ Feature: Status Desktop Sign Up | tester123 | Invalid34 | TesTEr16843/!@00 | | tester123 | TesTEr16843/!@) | TesTEr16843/!@01 | + @merge Scenario Outline: User cannot finish Sign Up and Sign In process with incorrect confirmation-again password Given A first time user lands on the status desktop and generates new key When the user inputs username @@ -123,6 +130,7 @@ Feature: Status Desktop Sign Up | lemon card easy goose keen divide cabbage daughter glide glad sense dice promote present august obey stay cheese | 0xdd06a08d469dd61Cb2E5ECE30f5D16019eBe0fc9 | | provide between target maze travel enroll edge churn random sight grass lion diet sugar cable fiction reflect reason gaze camp tone maximum task unlock | 0xCb59031d11D233112CB57DFd667fE1FF6Cd7b6Da | + @merge 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 @@ -131,11 +139,13 @@ Feature: Status Desktop Sign Up Then the following ui-component seedPhraseView_Submit_Button is not enabled And the invalid seed text is visible + @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 Then the user is online + @merge Scenario: User signs up with a profile image Given A first time user lands on the status desktop and generates new key diff --git a/test/ui-test/testSuites/suite_status/tst_ChatFlow/test.feature b/test/ui-test/testSuites/suite_status/tst_ChatFlow/test.feature index 9c55c76a94..6f39fa18ff 100644 --- a/test/ui-test/testSuites/suite_status/tst_ChatFlow/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_ChatFlow/test.feature @@ -14,6 +14,7 @@ Feature: Status Desktop Chat When user signs up with username tester123 and password TesTEr16843/!@00 Then the user lands on the signed in app + @mayfail Scenario: User joins a public room and chats When user joins chat room test Then user is able to send chat message @@ -23,12 +24,13 @@ Feature: Status Desktop Chat | I am from status | | tell me how you do? | - + @mayfail @merge Scenario: User can reply to their own message When user joins chat room test Then the user is able to send a random chat message Then the user can reply to the message at index 0 with "This is a reply" + @mayfail @merge Scenario: User can edit a message When user joins chat room test Then user is able to send chat message @@ -38,24 +40,25 @@ Feature: Status Desktop Chat Then the message (edited) is displayed in the last message - @mayfail + @mayfail @merge Scenario: User can reply to another user's message When user joins chat room test Then the user can reply to the message at index 0 with "This is a reply to another user" - + @mayfail @merge Scenario: User joins a room and marks it as read When user joins chat room test Then the user can mark the channel test as read # TODO find a way to validate that it worked - + @mayfail @merge Scenario: User can delete their own message When user joins chat room automation-test Then the user is able to send a random chat message Then the user can delete the message at index 0 Then the last message is not the random message + @mayfail @merge Scenario: User can clear chat history When user joins chat room test Then user is able to send chat message @@ -67,6 +70,7 @@ Feature: Status Desktop Chat When the user clears chat history Then the chat is cleared + @mayfail @merge Scenario: User can send a gif When the user opens the chat section And user joins chat room automation-test @@ -75,6 +79,7 @@ Feature: Status Desktop Chat And the user opens the messaging settings Then tenor GIFs preview is enabled + @mayfail @merge Scenario Outline: User can activate image unfurling When the user opens the chat section And user joins chat room automation-test @@ -91,6 +96,7 @@ Feature: Status Desktop Chat | image_url | | https://github.com/status-im/status-desktop/raw/master/test/ui-test/fixtures/images/doggo.jpeg | + @mayfail @merge Scenario: The user is able to use emoji suggestions When user joins chat room automation-test When the user types "hello :thumbs" @@ -99,13 +105,13 @@ Feature: Status Desktop Chat Then the message 👍 is displayed in the last message - @mayfail + @mayfail @merge Scenario: User cannot delete another user's message When user joins chat room test Then the user cannot delete the last message - @mayfail + @mayfail @merge Scenario Outline: The user can do a mention When user joins chat room test And the user inputs a mention to with message @@ -115,7 +121,7 @@ Feature: Status Desktop Chat | tester123 | testing mention | - @mayfail + @mayfail @merge Scenario Outline: The user can not do a mention to not existing users When user joins chat room test Then the user cannot input a mention to a not existing user @@ -124,6 +130,7 @@ Feature: Status Desktop Chat | notExistingAccount | | asdfgNoNo | + @mayfail @merge Scenario: User can send an emoji in a message When user joins chat room automation-test When user sends the emoji heart_eyes as a message @@ -132,7 +139,8 @@ Feature: Status Desktop Chat Then the emoji 😎 is displayed in the last message And the message wow I'm so cool is displayed in the last message - Scenario: User sees chats sorted by most recent activity + @mayfail @merge + Scenario: User sees chats sorted by most recent activity When user joins chat room first-chat And user joins chat room second-chat And user joins chat room third-chat @@ -147,13 +155,15 @@ Feature: Status Desktop Chat | third-chat | | first-chat | - Scenario: User can type message with emoji autoreplace + @mayfail @merge + Scenario: User can type message with emoji autoreplace When user joins chat room automation-test Then the user is able to send chat message "Hello :)" Then the message 🙂 is displayed in the last message And the message Hello is displayed in the last message + @mayfail @merge Scenario: User can send a sticker after installing a free pack When user joins chat room automation-test Then the user can install the sticker pack at position 4 diff --git a/test/ui-test/testSuites/suite_status/tst_communityFlows/test.feature b/test/ui-test/testSuites/suite_status/tst_communityFlows/test.feature index 4048e0f75e..baeb7e021d 100644 --- a/test/ui-test/testSuites/suite_status/tst_communityFlows/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_communityFlows/test.feature @@ -22,6 +22,7 @@ Feature: Status Desktop community When the user opens the community portal section Then the user lands on the community portal section + @merge Scenario Outline: User creates a community When the user creates a community named , with description , intro and outro Then the user lands on the community named @@ -31,6 +32,7 @@ Feature: Status Desktop community | testCommunity1 | Community tested 1 | My intro for the community | My community outro | + @merge @mayfail Scenario Outline: Admin creates a community channel When the user creates a community named myCommunity, with description My community description, intro Community Intro and outro Community Outro Then the user lands on the community named myCommunity @@ -42,7 +44,7 @@ Feature: Status Desktop community | test-channel | Community channel description tested 1 | bottom_menu | | test-channel2 | Community channel description tested 2 | right_click_menu | - + @mayfail Scenario Outline: Admin edits a community channel When the user creates a community named myCommunity, with description My community description, intro Community Intro and outro Community Outro Then the user lands on the community named myCommunity @@ -55,6 +57,7 @@ Feature: Status Desktop community | community_channel_name | community_channel_description | new_community_channel_name | | test-channel | Community channel description tested 1 | new-test-channel | + @merge @mayfail Scenario: Admin deletes a community channel When the user creates a community named myCommunity, with description My community description, intro Community Intro and outro Community Outro Then the user lands on the community named myCommunity @@ -65,6 +68,7 @@ Feature: Status Desktop community Then the channel count is 1 + @merge @mayfail Scenario Outline: Admin creates a community category When the user creates a community named myCommunity, with description My community description, intro Community Intro and outro Community Outro Then the user lands on the community named myCommunity @@ -89,6 +93,7 @@ Feature: Status Desktop community And the category named test-category is missing + @merge Scenario: Admin deletes a community category When the user creates a community named myCommunity, with description My community description, intro Community Intro and outro Community Outro Then the user lands on the community named myCommunity @@ -99,6 +104,7 @@ Feature: Status Desktop community Then the category named test-category is missing + @merge @mayfail Scenario Outline: Admin edits a community When the user creates a community named myCommunity, with description My community description, intro Community Intro and outro Community Outro Then the user lands on the community named myCommunity @@ -111,6 +117,7 @@ Feature: Status Desktop community | myCommunityNamedChanged | Cool new description 123 | #ff0000 | + @merge Scenario: User leaves community When the user creates a community named testCommunity, with description My community description, intro Community Intro and outro Community Outro Then the user lands on the community named testCommunity @@ -120,6 +127,7 @@ Feature: Status Desktop community Then the count of communities in navbar is 0 + @merge @mayfail Scenario Outline: User changes the emoji of a channel When the user creates a community named myCommunity, with description My community description, intro Community Intro and outro Community Outro Then the user lands on the community named myCommunity diff --git a/test/ui-test/testSuites/suite_status/tst_communityMessageFlows/test.feature b/test/ui-test/testSuites/suite_status/tst_communityMessageFlows/test.feature index d755353a0e..d43cebf6eb 100644 --- a/test/ui-test/testSuites/suite_status/tst_communityMessageFlows/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_communityMessageFlows/test.feature @@ -23,21 +23,24 @@ Feature: Status Desktop community messages When the user creates a community named test_community, with description Community description, intro community intro and outro commmunity outro Then the user lands on the community named test_community + @mayfail @merge Scenario: User sends a test image When the user sends a test image in the current channel Then the test image is displayed in the last message + @mayfail @merge Scenario: User sends a test image with a message When the user sends a test image in the current channel with message Mesage with an image Then the test image is displayed just before the last message And the message Mesage with an image is displayed in the last message + @mayfail @merge Scenario: User sends multiple test images with a message When the user sends multiple test images in the current channel with message Mesage with an image again Then the test images are displayed just before the last message And the message Mesage with an image again is displayed in the last message - + @mayfail @merge Scenario: User pins and unpins messages # This one wont work until #6554 is fixed # And the amount of pinned messages is 0 diff --git a/test/ui-test/testSuites/suite_status/tst_groupChat/test.feature b/test/ui-test/testSuites/suite_status/tst_groupChat/test.feature index 0a208720c9..8c5c8820da 100644 --- a/test/ui-test/testSuites/suite_status/tst_groupChat/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_groupChat/test.feature @@ -38,6 +38,7 @@ Feature: Status Desktop Group Chat # TODO: Add cleanup scenario. Leave, one by one, the chat + @mayfail @merge Scenario: As an admin user I want to change group chat's name, color and image When the user creates a group chat adding users | Athletic | diff --git a/test/ui-test/testSuites/suite_status/tst_languageSettings/test.feature b/test/ui-test/testSuites/suite_status/tst_languageSettings/test.feature index e1ae201b97..5bf524bff1 100644 --- a/test/ui-test/testSuites/suite_status/tst_languageSettings/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_languageSettings/test.feature @@ -39,27 +39,28 @@ Feature: Status Language Settings | Arabic | العربية | #| Bengali | বাংলা | #| Chinese (China) | 中文（中國） | - | Chinese (Taiwan) | 中文（台灣） | + #| Chinese (Taiwan) | 中文（台灣） | #| Dutch | Nederlands | #| French | Français | #| German | Deutsch | #| Hindi | हिन्दी | #| Indonesian | Bahasa Indonesia | #| Italian | Italiano | - | Japanese | 日本語 | + #| Japanese | 日本語 | #| Korean | 한국어 | #| Malay | Bahasa Melayu | #| Polish | Polski | #| Portuguese | Português | - | Portuguese (Brazil) | Português (Brasil) | + #| Portuguese (Brazil) | Português (Brasil) | #| Russian | Русский | #| Spanish | Español | #| Spanish (Latin America) | Español (Latinoamerica) | #| Spanish (Argentina) | Español (Argentina) | #| Tagalog | Tagalog | - | Turkish | Türkçe | + #| Turkish | Türkçe | # Each language run takes 30 seconds, so only some of them are enabled until we can parallelize executions + @merge Scenario Outline: The user is able to search and select a specific language and after a restart, the language is kept When the user opens the language selector And the user searches the language @@ -73,7 +74,7 @@ Feature: Status Language Settings Then the application displays as the selected language Examples: | language | native | - | English | English | + #| English | English | #| Arabic | العربية | #| Bengali | বাংলা | #| Chinese (China) | 中文（中國） | @@ -87,12 +88,12 @@ Feature: Status Language Settings #| Japanese | 日本語 | #| Korean | 한국어 | #| Malay | Bahasa Melayu | - | Polish | Polski | + #| Polish | Polski | #| Portuguese | Português | #| Portuguese (Brazil) | Português (Brasil) | #| Russian | Русский | #| Spanish | Español | #| Spanish (Latin America) | Español (Latinoamerica) | #| Spanish (Argentina) | Español (Argentina) | - | Tagalog | Tagalog | + #| Tagalog | Tagalog | #| Turkish | Türkçe | \ No newline at end of file diff --git a/test/ui-test/testSuites/suite_status/tst_searchFlows/test.feature b/test/ui-test/testSuites/suite_status/tst_searchFlows/test.feature index 3cb684c213..66ea566ae7 100644 --- a/test/ui-test/testSuites/suite_status/tst_searchFlows/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_searchFlows/test.feature @@ -30,18 +30,21 @@ Feature: Search feature (ctrl+F) # Go back to the portal so that we see if the search really redirects When the user opens the community portal section + @merge @mayfail Scenario: User can search for a community channel When the user opens the search menu And the user searches for automation And the user clicks on the search result for channel automation-community Then the user lands on the channel named automation-community + @merge @mayfail Scenario: User can search for a public channel When the user opens the search menu And the user searches for automation And the user clicks on the search result for channel search-automation-test-2 Then the chat title is search-automation-test-2 + @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 diff --git a/test/ui-test/testSuites/suite_status/tst_settingsMenu/test.feature b/test/ui-test/testSuites/suite_status/tst_settingsMenu/test.feature index 522b375caf..6c6dade96d 100644 --- a/test/ui-test/testSuites/suite_status/tst_settingsMenu/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_settingsMenu/test.feature @@ -9,15 +9,18 @@ Feature: Status Desktop Settings Menu 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 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 his state to offline When the users switches his state to offline Then the user appears offline @@ -25,6 +28,7 @@ Feature: Status Desktop Settings Menu And the user tester123 logs in with password TesTEr16843/!@00 Then the user appears offline + @merge Scenario: The user can switch his state to online When the users switches his state to offline And the user restarts the app diff --git a/test/ui-test/testSuites/suite_status/tst_statusLoginPassword/test.feature b/test/ui-test/testSuites/suite_status/tst_statusLoginPassword/test.feature index 3ca654bba8..1a661fe255 100644 --- a/test/ui-test/testSuites/suite_status/tst_statusLoginPassword/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_statusLoginPassword/test.feature @@ -26,10 +26,9 @@ Feature: Status Desktop login Examples: | username | password | | Athletic_Prime | TesTEr16843/!@00 | - | Nervous_Pesky | TesTEr16843/!@11 | - | Granular_Diligent| TesTEr16843/!@22 | + @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 and password diff --git a/test/ui-test/testSuites/suite_status/tst_transaction/test.feature b/test/ui-test/testSuites/suite_status/tst_transaction/test.feature index c1a726b4f2..42a5ba6039 100644 --- a/test/ui-test/testSuites/suite_status/tst_transaction/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_transaction/test.feature @@ -2,30 +2,31 @@ Feature: Status Desktop Transaction As a user I want to perform transaction - # Background: Sign up & Enable wallet section & Toggle test networks - # 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 - # 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 - # And the user toggles test networks - # And the user opens wallet screen - # And the user accepts the signing phrase + Background: Sign up & Enable wallet section & Toggle test networks + 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 + 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 + And the user toggles test networks + And the user opens wallet screen + And the user accepts the signing phrase - # Scenario Outline: User sends a transaction - # When the user sends a transaction to himself from account Status account of on with password qqqqqqqqqq - # Then the transaction is in progress + @mayfail + Scenario Outline: User sends a transaction + When the user sends a transaction to himself from account Status account of on with password qqqqqqqqqq + Then the transaction is in progress - # Examples: - # | amount | token | chain_name | - # | 1 | ETH | Goerli | - # | 0 | ETH | Goerli | - # | 1 | STT | Goerli | - # | 0 | STT | Goerli | + Examples: + | amount | token | chain_name | + | 1 | ETH | Goerli | + | 0 | ETH | Goerli | + | 1 | STT | Goerli | + | 0 | STT | Goerli | - # @mayfail - # Scenario: User registers a ENS name - # When the user registers a random ens name with password qqqqqqqqqq - # Then the transaction is in progress + @mayfail + Scenario: User registers a ENS name + When the user registers a random ens name with password qqqqqqqqqq + Then the transaction is in progress diff --git a/test/ui-test/testSuites/suite_status/tst_userIdentity/test.feature b/test/ui-test/testSuites/suite_status/tst_userIdentity/test.feature index 19c0685ff0..d0b06c7a57 100644 --- a/test/ui-test/testSuites/suite_status/tst_userIdentity/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_userIdentity/test.feature @@ -7,6 +7,7 @@ Feature: User Identity When user signs up with username tester123 and password TesTEr16843/!@00 Then the user lands on the signed in app + @mayfail Scenario: User sets display name, bio and social links When the user opens app settings screen And the user opens the profile settings @@ -25,6 +26,7 @@ Feature: User Identity And the user's bio should be "Hello, I am super tester!" And the user's social links should be: "twitter_handle", personal site: "status.im", "customLink": "customUrl" + @merge Scenario: The user sets can change own display name in profile popup When the user opens own profile popup Then in profile popup the user's display name should be "tester123" diff --git a/test/ui-test/testSuites/suite_status/tst_wallet/config.xml b/test/ui-test/testSuites/suite_status/tst_wallet/config.xml new file mode 100644 index 0000000000..99a36badcd --- /dev/null +++ b/test/ui-test/testSuites/suite_status/tst_wallet/config.xml @@ -0,0 +1,10 @@ + + + + + + +~mayfail + + + diff --git a/test/ui-test/testSuites/suite_status/tst_wallet/test.feature b/test/ui-test/testSuites/suite_status/tst_wallet/test.feature index 8b70ba1e7e..d0b552cddd 100644 --- a/test/ui-test/testSuites/suite_status/tst_wallet/test.feature +++ b/test/ui-test/testSuites/suite_status/tst_wallet/test.feature @@ -10,6 +10,7 @@ Feature: Status Desktop Wallet When the user activates wallet and opens the wallet section When the user accepts the signing phrase + @mayfail Scenario Outline: User adds a watch only account When the user adds watch only account with and
Then the new account is added @@ -23,12 +24,14 @@ Feature: Status Desktop Wallet Scenario Outline: User generates a new account from wallet When the user generates a new account with and TesTEr16843/!@00 Then the new account is added + When the user deletes the account + Then the account is not in the list of accounts Examples: | account_name | | one | - | two | + @mayfail Scenario Outline: User imports a private key When the user imports a private key with and TesTEr16843/!@00 and Then the new account is added @@ -37,6 +40,7 @@ Feature: Status Desktop Wallet | account_name | private_key | | one | 8da4ef21b864d2cc526dbdb2a120bd2874c36c9d0a1fb7f8c63d7f7a8b41de8f | + @mayfail Scenario Outline: User imports a seed phrase When the user imports a seed phrase with and TesTEr16843/!@00 and Then the new account is added @@ -45,24 +49,13 @@ Feature: Status Desktop Wallet | account_name | seed_phrase | | one | indoor dish desk flag debris potato excuse depart ticket judge file exit | - Scenario Outline: User deletes a generated account - When the user generates a new account with and TesTEr16843/!@00 - And the user deletes the account - Then the account is not in the list of accounts - Examples: - | account_name | - | one | - - Scenario Outline: User adds a saved address - When the user adds a saved address named and address
- Then the name is in the list of saved addresses - - Examples: - | name | address | - | one | 0x8397bc3c5a60a1883174f722403d63a8833312b7 | - - Scenario Outline: User can edit a saved address + Scenario Outline: User can manage a saved address + When the user adds a saved address named and address
+ And the user toggles favourite for the saved address with name + Then the saved address has favourite status true + When the user deletes the saved address with name + Then the name is not in the list of saved addresses When the user adds a saved address named and address
And the user edits a saved address with name to Then the name is in the list of saved addresses @@ -71,27 +64,7 @@ Feature: Status Desktop Wallet | name | address | new_name | | bar | 0x8397bc3c5a60a1883174f722403d63a8833312b7 | foo | - Scenario Outline: User can delete a saved address - When the user adds a saved address named and address
- And the user deletes the saved address with name - Then the name is not in the list of saved addresses - - Examples: - | name | address | - | one | 0x8397bc3c5a60a1883174f722403d63a8833312b7 | - - Scenario Outline: User can toggle favourite for a saved address - When the user adds a saved address named and address
- And the user toggles favourite for the saved address with name - Then the saved address has favourite status true - When the user toggles favourite for the saved address with name - Then the saved address has favourite status false - - Examples: - | name | address | - | favourite | 0x8397bc3c5a60a1883174f722403d63a8833312b7 | - - @onlythis + @mayfail Scenario: User can toggle network and see balances When the user opens app settings screen And the user opens the wallet settings @@ -102,6 +75,7 @@ Feature: Status Desktop Wallet And the user has a positive balance of ETH And the user has a positive balance of STT + @mayfail Scenario Outline: User can edit the default wallet account When the user opens app settings screen And the user opens the wallet settings @@ -113,6 +87,7 @@ Feature: Status Desktop Wallet | new_name | new_color | | Default | #FFCA0F | + @mayfail Scenario Outline: Can see collectibles for an account When the user adds watch only account with and
Then the collectibles are listed for the