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_messaging/tst_ChatFlow/test.feature

168 lines
7.2 KiB
Gherkin
Raw Normal View History

test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Feature: Status Desktop Chat Basic Flows
feat(@DesktopApp): Basic Chat Scenario (Squish Test) Ticket: https://github.com/status-im/status-desktop/issues/5718 Include Basic chat Scenario
2022-06-07 15:19:52 +00:00
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
As a user I want to join the public chat room "test" and do basic interactions.
feat(@DesktopApp): Basic Chat Scenario (Squish Test) Ticket: https://github.com/status-im/status-desktop/issues/5718 Include Basic chat Scenario
2022-06-07 15:19:52 +00:00
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
The following scenarios cover basic chat flows on "test" public channel.
feat(@DesktopApp): Basic Chat Scenario (Squish Test) Ticket: https://github.com/status-im/status-desktop/issues/5718 Include Basic chat Scenario
2022-06-07 15:19:52 +00:00
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +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 "test"
feat(@DesktopApp): Basic Chat Scenario (Squish Test) Ticket: https://github.com/status-im/status-desktop/issues/5718 Include Basic chat Scenario
2022-06-07 15:19:52 +00:00
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
[Cleanup] Also each scenario starts with:
** when the user opens the chat section
# TODO: Add scenario end -> clear chat input.
Scenario Outline: The user can chat in a public room
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 sends a chat message "<message>"
Then the last chat message contains "<message>"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Examples:
feat(@DesktopApp): Basic Chat Scenario (Squish Test) Ticket: https://github.com/status-im/status-desktop/issues/5718 Include Basic chat Scenario
2022-06-07 23:47:19 +00:00
| message |
| Hello |
| How are you |
| I am from status |
| tell me how you do? |
test(chat): add test to reply a message Fixes #6670
2022-07-28 18:58:19 +00:00
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
@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.
tests(suite_messaging): properly check if reply message has reply Prior to this commit we were merely checking if the message in question was the last one. With this commit we now check whether there's a reply in the first place and whether the reply-to-message is the correct one. We also distinguish whether the message we're replying to is the one from the loggedin user (and not someone else's)
2022-11-15 14:58:11 +00:00
Scenario Outline: The user can reply to own message
Given the user sends a chat message "<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
When the user replies to the message at index 0 with "<reply>"
tests(suite_messaging): properly check if reply message has reply Prior to this commit we were merely checking if the message in question was the last one. With this commit we now check whether there's a reply in the first place and whether the reply-to-message is the correct one. We also distinguish whether the message we're replying to is the one from the loggedin user (and not someone else's)
2022-11-15 14:58:11 +00:00
Then the chat message "<reply>" is displayed as a reply of this user's "<message>"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Examples:
tests(suite_messaging): properly check if reply message has reply Prior to this commit we were merely checking if the message in question was the last one. With this commit we now check whether there's a reply in the first place and whether the reply-to-message is the correct one. We also distinguish whether the message we're replying to is the one from the loggedin user (and not someone else's)
2022-11-15 14:58:11 +00:00
| message | reply |
| random chat message | This is a reply |
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
@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
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
Given the user sends a chat message "Edit me"
When the user edits the message at index 0 and changes it to "<edited>"
Then the chat message "<edited>" is displayed as an edited one
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Examples:
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
| edited |
| Edited by me |
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
@relyon-mailserver
Scenario Outline: The user can reply to another 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
When the user replies to the message at index 0 with "<reply>"
Then the chat message "<reply>" is displayed as a reply
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
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
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
# Scenario: The user joins a room and marks it as read
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
# When the user joins chat room test
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 marks the channel "test" as read
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
# # TODO find a way to validate that it worked
@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
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
Given the user sends a chat message "<message>"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
When the user deletes the message at index 0
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 last message displayed is not "<message>"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Examples:
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
| message |
| random chat message |
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Scenario: The user can clear chat history
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
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"
test(chat): Can clean chat history Closes: #6876
2022-08-15 17:16:01 +00:00
When the user clears chat history
Then the chat is cleared
fix(tests): Fixed message reply test
2022-08-25 08:27:20 +00:00
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
@mayfail
# TODO: Verification of gif sent fails. And also `tenor GIFs preview is enabled` step doesn't work. Review it.
Scenario: The user can send a GIF
Given the user opens app settings screen
And the user opens the messaging settings
And tenor GIFs preview is enabled
When the user sends a GIF message
Then the GIF message is displayed
@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
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
Given the user sends a chat message "<image_url>"
And the image "<image_url>" is not unfurled in the chat
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
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
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 image "<image_url>" is unfurled in the chat
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Examples:
| image_url |
| https://github.com/status-im/status-desktop/raw/master/test/ui-test/fixtures/images/doggo.jpeg |
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
Scenario: The user is able to use emoji suggestions
Given the user types "hello :thumbs"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
And the user selects the emoji in the suggestion's list
When the user presses enter
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 last chat message contains "👍"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
@relyon-mailserver
Scenario: The user cannot delete another user's message
test(tags): add ignore tags to tests that have a chance to fail
2022-08-12 18:55:06 +00:00
Then the user cannot delete the last message
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
@relyon-mailserver
test(tags): add ignore tags to tests that have a chance to fail
2022-08-12 18:55:06 +00:00
Scenario Outline: The user can do a mention
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 inputs a mention to "<displayName>" with message "<message>"
Then the "<displayName>" mention with message "<message>" have been sent
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Examples:
test(tags): add ignore tags to tests that have a chance to fail
2022-08-12 18:55:06 +00:00
| displayName | message |
| tester123 | testing mention |
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
@relyon-mailserver
Scenario Outline: The user can not do a mention to a not existing users
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 user cannot input a mention to a not existing user "<displayName>"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Examples:
test(tags): add ignore tags to tests that have a chance to fail
2022-08-12 18:55:06 +00:00
| displayName |
| notExistingAccount |
test(chat): add test that sends a message with an emoji Fixes #6881
2022-08-12 18:42:06 +00:00
| asdfgNoNo |
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Scenario: The user can send an emoji as a 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
When the user sends the emoji "heart_eyes" as a message
Then the last chat message contains "😍"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Scenario Outline: The user can send an emoji in a 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
When the user sends the emoji "sunglasses" with message "<message>"
Then the last chat message contains "😎"
And the last chat message contains "<message>"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Examples:
| message |
| wow I'm so cool |
# 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
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 "first-chat"
# And the user joins chat room "second-chat"
# And the user joins chat room "third-chat"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
# Then the user chats are sorted accordingly
# | third-chat |
# | second-chat |
# | first-chat |
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 switches to "second-chat" chat
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
# And the user sends a random chat message
# Then the random chat message is displayed
# And the user chats are sorted accordingly
# | second-chat |
# | third-chat |
# | first-chat |
Scenario: The user can type message with emoji autoreplace
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 sends a chat message "Hello :)"
Then the last chat message contains "🙂"
And the last chat message contains "Hello"
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
test(suite_messaging/tst_ChatFlow): Added tag `mayfail` bc it is weak on the CI Disabled test case since it is weak on the CI. It works standalone but when it runs as part of the sequence and mostly in the CI, the action of verification doesn't work.
2022-10-21 07:17:48 +00:00
@mayfail
# TODO: It works standalone but when it runs as part of the sequence and mostly in the CI, the action of verification doesn't work.
test(chore/suite_messaging): Added specific `bdd_hooks` for `suite_messaging/tst_ChatFlow` - Reviewed `suite_messaging/tst_ChatFlow` feature: Cleanup of duplicated steps and separation of action / validation applied. - Reviewed `suite_messaging/tst_groupChat` feature. - Added new tag to `Jenkins` file: `relyon-mailserver`. - Added new `StartupSteps` class to manage init / startup static methods outside bdd steps. It can be used as a util in `hooks` and `steps`. Closes #7931
2022-10-13 16:03:10 +00:00
Scenario: The user can send a sticker after installing a free pack
Given the user installs the sticker pack at position 4
When the user sends the sticker at position 2 in the list
Then the last chat message is a sticker