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_communities/tst_searchFlows/test.feature

59 lines
2.7 KiB
Gherkin
Raw Normal View History

test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
#******************************************************************************
# Status.im
#*****************************************************************************/
#/**
# * \file test.feature
# *
# * \test Status Desktop - Search flows
# * \date August 2022
# **
# *****************************************************************************/
Feature: Search feature (ctrl+F)
As a user, I want to search the different chats and messages of the app
Covers the search flows
Background:
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 "tester123" and password "TesTEr16843/!@00"
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
Then the user lands on the signed in 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
When the user joins chat room "search-automation-test-1"
And the user joins chat room "search-automation-test-2"
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
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
Then the user lands on the community named myCommunity
When the admin creates a community channel named automation-community, with description My description with the method bottom_menu
Then the user lands on the channel named automation-community
# Go back to the portal so that we see if the search really redirects
When the user opens the community portal section
test: add merge tag + add missing mayfail
2022-09-20 12:22:04 +00:00
@merge @mayfail
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
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
test: add merge tag + add missing mayfail
2022-09-20 12:22:04 +00:00
@merge @mayfail
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
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
test: add merge tag + add missing mayfail
2022-09-20 12:22:04 +00:00
@mayfail
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
Scenario: User can search for a message in a public channel
When the user opens the chat section
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 joins chat room "search-automation-test-1"
fix(tests): Fixed message reply test
2022-08-25 08:27:20 +00:00
Then the user is able to send a random chat message
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
# Go back to the portal so that we see if the search really redirects
When the user opens the community portal section
And the user opens the search menu
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
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
Then the chat title is "search-automation-test-1"