Skip to content

Commit

Permalink
add missing steps
Browse files Browse the repository at this point in the history
  • Loading branch information
yasserfaraazkhan committed Nov 14, 2024
1 parent 2401ed3 commit 146a3be
Show file tree
Hide file tree
Showing 3 changed files with 46 additions and 3 deletions.
17 changes: 16 additions & 1 deletion data/test-cases/channels/scheduled-messages/MM-T5650.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ key: MM-T5650
created_on: "2024-11-13T01:45:31Z"
last_updated: "2024-11-13T07:15:31Z"
case_hashed: 6f6ff10705310d195ea15dd491c33ce774c456bfd3bb7de0b5295cda9dae46bba414fa6a69aa0b3ae44d89a74b00990d
steps_hashed: da75d1744a55f6be35e72a266c93e6411d01ad3708cf79984b9b6d5d4cdc94be81c6da13a479fde3e4750c567abb0353
steps_hashed: 84a8c287643ca0f92c5dc7c87453598bc1472689481ba1283c5fe74ba1385369341c683377453819c37ca8336d598189
---

<!-- (Auto-generated) Based on frontmatter's "key" and "name" -->
Expand All @@ -40,3 +40,18 @@ steps_hashed: da75d1744a55f6be35e72a266c93e6411d01ad3708cf79984b9b6d5d4cdc94be81
---

**Step 1**

### Scenario 1: Able to copy the contents of a scheduled message.

Steps:

1. Log into User's account.
2. Type a message in the GM/Channel post text box.
3. Click on the Dropdown beside Send button.
4. Click on `Choose a custom time`.
5. Click On `Schedule` button with the default date and time of scheduled post.
6. Go to Scheduled tab and verify the messages appears.
7. Hover on the scheduled message.
8. Click on `Copy` icon.
9. Go to the channel and paste the copied content as a message.
10. Verify the Scheduled message content and recent posted message content are same.
16 changes: 15 additions & 1 deletion data/test-cases/channels/scheduled-messages/MM-T5651.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ key: MM-T5651
created_on: "2024-11-13T01:45:32Z"
last_updated: "2024-11-13T07:15:31Z"
case_hashed: cf1abcb5fa97e9d7725ab99a4b9abbfc78fb6d19f807dd0c8c788214a58832a381ed13df66e5a1e18d753720e89730ba
steps_hashed: da75d1744a55f6be35e72a266c93e6411d01ad3708cf79984b9b6d5d4cdc94be81c6da13a479fde3e4750c567abb0353
steps_hashed: 5ed539e26c43b56028ad5f808bde4e3038ee52fa9b2a152fc4d11bf548e57f30ad1f0ceef0b077164913d685e66e3c26
---

<!-- (Auto-generated) Based on frontmatter's "key" and "name" -->
Expand All @@ -40,3 +40,17 @@ steps_hashed: da75d1744a55f6be35e72a266c93e6411d01ad3708cf79984b9b6d5d4cdc94be81
---

**Step 1**

### Scenario 1: Able to see most recent custom time when scheduling a message

Steps:

1. Log into User's account.
2. Type a message in the GM/Channel post text box.
3. Click on the Dropdown beside Send button.
4. Click on `Choose a custom time`.
5. Choose a future date and time.
6. Click on scehdule button.
7. Verify the message is scehduled.
8. Compose another schedule message and click on the Dropdown beside Send button.
9. Verify the user can see the recent custom Date and time used to schedule.
16 changes: 15 additions & 1 deletion data/test-cases/channels/scheduled-messages/MM-T5652.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ key: MM-T5652
created_on: "2024-11-13T01:45:33Z"
last_updated: "2024-11-13T07:15:32Z"
case_hashed: ba8e2494f476e241afee96936371b1ab752b93230f6d242ea9ce9cf61958ccc7cf63b01361562c5962367067e51154a0
steps_hashed: da75d1744a55f6be35e72a266c93e6411d01ad3708cf79984b9b6d5d4cdc94be81c6da13a479fde3e4750c567abb0353
steps_hashed: a1e05b0d91dfcf6b0544b111bb61eb3bf66425eb3f73264d9bb66ff7cf02461a3a172d718d1ff44854ea5ff85dfc5e8b
---

<!-- (Auto-generated) Based on frontmatter's "key" and "name" -->
Expand All @@ -40,3 +40,17 @@ steps_hashed: da75d1744a55f6be35e72a266c93e6411d01ad3708cf79984b9b6d5d4cdc94be81
---

**Step 1**

### Scenario 1: Able to see schedule a message in a shared channel.

Test setup:

1. Have 2 mattermost instances that have a shared channel.

Steps:

1. Log into First mattermost instance.
2. Go to the shared channel and schedule a message.
3. Log into Sendond mattermost instance.
4. Go to the shared channel.
5. Verify the scheduled message has arrived successfully

0 comments on commit 146a3be

Please sign in to comment.