2022-06-07 15:19:52 +00:00
# This is a sample .feature file
# Squish feature files use the Gherkin language for describing features, a short example
# is given below. You can find a more extensive introduction to the Gherkin format at
# https://cucumber.io/docs/gherkin/reference/
Feature : Status Desktop Chat
2022-08-10 06:57:34 +00:00
# TODO The complete feature / all scenarios have a chance to fail since they rely on the mailserver (at least, to verify a chat is loaded, something in the history needs to be displayed).
A s a u s e r I w a n t t o j o i n a r o o m a n d c h a t a n d d o b a s i c i n t e r a c t i o n s .
2022-06-07 15:19:52 +00:00
T h e f o l l o w i n g s c e n a r i o s c o v e r b a s i c c h a t f l o w s .
Background :
Given A f i r s t t i m e u s e r l a n d s o n t h e s t a t u s d e s k t o p a n d g e n e r a t e s n e w k e y
2022-06-16 01:46:45 +00:00
When u s e r s i g n s u p w i t h u s e r n a m e t e s t e r 123 a n d p a s s w o r d T e s T E r 16843 / ! @ 00
2022-06-07 15:19:52 +00:00
Then t h e u s e r l a n d s o n t h e s i g n e d i n a p p
2022-08-10 06:57:34 +00:00
Scenario : User joins a public room and chats
2022-06-07 15:19:52 +00:00
When u s e r j o i n s c h a t r o o m t e s t
2022-06-07 23:37:11 +00:00
Then u s e r i s a b l e t o s e n d c h a t m e s s a g e
2022-06-07 23:47:19 +00:00
| m e s s a g e |
| H e l l o |
| H o w a r e y o u |
| I a m f r o m s t a t u s |
| t e l l m e h o w y o u d o ? |
2022-07-28 18:58:19 +00:00
2022-07-28 20:14:29 +00:00
2022-07-28 18:58:19 +00:00
Scenario : User can reply to their own message
When u s e r j o i n s c h a t r o o m t e s t
Then u s e r i s a b l e t o s e n d c h a t m e s s a g e
| m e s s a g e |
| R e p l y t o t h i s |
Then t h e u s e r c a n r e p l y t o t h e m e s s a g e a t i n d e x 0 w i t h " T h i s i s a r e p l y "
2022-07-28 20:14:29 +00:00
2022-07-28 18:58:19 +00:00
# TODO This test has a chance to fail since it relies on the mailserver. Until we host a local mailserver for the tests, this test is at risk
2022-08-05 19:52:34 +00:00
# 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"
2022-07-28 20:14:29 +00:00
Scenario : User joins a room and marks it as read
When u s e r j o i n s c h a t r o o m t e s t
Then t h e u s e r c a n m a r k t h e c h a n n e l t e s t a s r e a d
# TODO find a way to validate that it worked
2022-08-02 20:04:29 +00:00
Scenario : User can delete their own message
When u s e r j o i n s c h a t r o o m a u t o m a t i o n - t e s t
2022-08-05 19:52:34 +00:00
Then u s e r i s a b l e t o s e n d a r a n d o m c h a t m e s s a g e
2022-08-02 20:04:29 +00:00
Then t h e u s e r c a n d e l e t e t h e m e s s a g e a t i n d e x 0
2022-08-05 19:52:34 +00:00
Then t h e l a s t m e s s a g e i s n o t t h e r a n d o m m e s s a g e
2022-08-02 20:04:29 +00:00
# TODO This test has a chance to fail since it relies on the mailserver. Until we host a local mailserver for the tests, this test is at risk
2022-08-05 19:52:34 +00:00
# Scenario: User cannot delete another user's message
# When user joins chat room test
# Then the user cannot delete the last message
2022-08-10 06:57:34 +00:00
# Scenario Outline: The user can do a mention
# When user joins chat room test
# And 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 |
# 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 <displayName>
# Examples:
# | displayName |
# | notExistingAccount |
# | asdfgNoNo |
