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

67 lines
3.1 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
test(suite_communities): Created `bdd_hook` for each `suite_communities` test case - Created `bdd_hooks` that contain the sing up steps just only once in the feature start and the needed start steps depending on the test case. - Updated feature files removing sign up steps and given/when/then reorganization. - Done some cleanups and reorganization in `communitySteps.py` and `searchSteps.py`. Closes #7955
2022-10-25 12:44:28 +00:00
The feature start sequence is the following (setup on its own `bdd_hooks`):
** 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"
** and the user lands on the signed in app
** and user joins chat room "search-automation-test-1"
** and user joins chat room "search-automation-test-2"
** given the user opens the community portal section
** and the user lands on the community portal section
** and the user creates a community named "myCommunity", with description "My community description", intro "Community Intro" and outro "Commmunity outro"
** and the user lands on the community named "myCommunity"
** and the admin creates a community channel named "automation-community", with description "My description" with the method "bottom_menu"
** and the user lands on the channel named "automation-community"
Background:
# It starts opening the portal so that we see if the search really redirects
Given the user opens the community portal section
And the user lands on the community portal section
@mayfail
# myfail because of dekstop issue #7989. Once it is fixed, remove tag.
Scenario: The user can search for a community channel
Given the user opens the search menu
And the user searches for "automation"
When the user clicks on the search result for channel "automation-community"
Then the channel named "automation-community" is open
@mayfail
# myfail because of dekstop issue #7989. Once it is fixed, remove tag.
Scenario: The user can search for a public channel
Given the user opens the search menu
And the user searches for "automation"
When the user clicks on the search result for channel "search-automation-test-2"
Then the chat title is "search-automation-test-2"
@mayfail
# myfail because of desktop issue #7989. Once it is fixed, remove tag.
Scenario: The user can search for a message in a public channel
Given 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"
test(suite_communities): Created `bdd_hook` for each `suite_communities` test case - Created `bdd_hooks` that contain the sing up steps just only once in the feature start and the needed start steps depending on the test case. - Updated feature files removing sign up steps and given/when/then reorganization. - Done some cleanups and reorganization in `communitySteps.py` and `searchSteps.py`. Closes #7955
2022-10-25 12:44:28 +00:00
And the user sends 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
test(suite_communities): Created `bdd_hook` for each `suite_communities` test case - Created `bdd_hooks` that contain the sing up steps just only once in the feature start and the needed start steps depending on the test case. - Updated feature files removing sign up steps and given/when/then reorganization. - Done some cleanups and reorganization in `communitySteps.py` and `searchSteps.py`. Closes #7955
2022-10-25 12:44:28 +00:00
And the user opens the community portal section
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
And the user opens the search menu
test(suite_communities): Created `bdd_hook` for each `suite_communities` test case - Created `bdd_hooks` that contain the sing up steps just only once in the feature start and the needed start steps depending on the test case. - Updated feature files removing sign up steps and given/when/then reorganization. - Done some cleanups and reorganization in `communitySteps.py` and `searchSteps.py`. Closes #7955
2022-10-25 12:44:28 +00:00
When the user searches the random message
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
Then the search menu shows 1 results
test(suite_communities): Created `bdd_hook` for each `suite_communities` test case - Created `bdd_hooks` that contain the sing up steps just only once in the feature start and the needed start steps depending on the test case. - Updated feature files removing sign up steps and given/when/then reorganization. - Done some cleanups and reorganization in `communitySteps.py` and `searchSteps.py`. Closes #7955
2022-10-25 12:44:28 +00:00
test(search): add test for the search feature Fixes #6885
2022-08-15 21:01:12 +00:00
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"