add tests

data/test-by-folder.json

@@ -1606,6 +1606,8 @@
       "Verify User can create a scheduled message in DM/GM/Channel",
       "Verify User can identify the cases for failed scheduled message",
       "Verify User can remove scheduled setting from a scheduled message",
+      "Verify User can see most recent time used in the Send button dropdown option",
+      "Verify User schedule a message in a shared channel",
       "Verify if the Failed scheduled message is sent out after server recovered from an outage issue"
     ]
   },

data/test-cases/channels/schedule-messages/1-Copy-Contents.md

@@ -33,7 +33,7 @@ case_hashed: null
 steps_hashed: null
 ---
 
-### Scenario 1: Able to add schedule to the Draft message.
+### Scenario 1: Able to copy the contents of a scheduled message.
 
 Steps:
 
@@ -45,5 +45,5 @@ Steps:
 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 post the copied content as a message.
+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.

data/test-cases/channels/schedule-messages/2-Most-Recent_times.md

@@ -0,0 +1,48 @@
+---
+# (Required) Ensure all values are filled up
+name: "Verify User can see most recent time used in the Send button dropdown option"
+status: Active
+priority: Normal
+folder: Schedule Messages
+authors: "@yasserfaraazkhan"
+team_ownership:
+- ICU
+priority_p1_to_p4: P3 - Deep Functions (Do extensive scenarios work?)
+
+# (Optional)
+location: Messaging
+component: null
+tags: []
+labels: []
+tested_by_contributor: ""
+
+# (Optional) Test type and tools
+cypress: N/A
+detox: N/A
+mmctl: N/A
+playwright: N/A
+rainforest: []
+manual_test_environments: []
+
+# Do not change
+id: null
+key: null
+created_on: null
+last_updated: null
+case_hashed: null
+steps_hashed: null
+---
+
+### 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.

data/test-cases/channels/schedule-messages/3-Shared-Channel.md

@@ -0,0 +1,48 @@
+---
+# (Required) Ensure all values are filled up
+name: "Verify User schedule a message in a shared channel"
+status: Active
+priority: Normal
+folder: Schedule Messages
+authors: "@yasserfaraazkhan"
+team_ownership:
+- ICU
+priority_p1_to_p4: P3 - Deep Functions (Do extensive scenarios work?)
+
+# (Optional)
+location: Messaging
+component: null
+tags: []
+labels: []
+tested_by_contributor: ""
+
+# (Optional) Test type and tools
+cypress: N/A
+detox: N/A
+mmctl: N/A
+playwright: N/A
+rainforest: []
+manual_test_environments: []
+
+# Do not change
+id: null
+key: null
+created_on: null
+last_updated: null
+case_hashed: null
+steps_hashed: null
+---
+
+### 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