Page Comparison

Test ID

Test Case

Test Steps

Result

Notes

100

A checklist item configured without a slash command does not have a Run button next to it

1. Log in as user-1.

2. Launch playbook backstage.

3. Click “New Playbook”.

4. Enter “Apb” as the playbook name.

5. Change the name of “Default Stage” to “S1”.

6. Click “Add new checklist item”.

7. Enter “C1” as the item name.

8. Don’t add anything for the slash command.

9. Save playbook.

10. Switch to normal channel view.

11. Start a new incident using “Apb”.

12. Once the incident is started, in the incident RHS, examine the checklist item “C1” under “S1”.

13. Verify that “C1” does not have any “Run” button.

101

A checklist item configured with a valid slash command has a Run button next to it

Continue from the above test.

1. Launch playbook.

2. Find and click “Apb” to edit.

3. Add slash command /away for “C1”.

4. Switch to normal channel view.

5. Start a new incident using “Apb”.

6. Once the incident is started, in the incident RHS, verify that “C1” show /away under it which has a Run button next to it.

102

A checklist item configured with an invalid slash command does not have a Run button next to it

Continue from the above test.

1. Launch playbook backstage.

2. Find and click “Apb” to edit.

3. Add a new checklist item “C2” under “S1”.

4. Add slash command invalid text for “C2”.

5. Save playbook.

6. Switch to normal channel view.

7. Start a new incident using “Apb”.

8. Once the incident has started, find “C2” under “S1”.

9. Verify that the slash command for “C2” doesn’t have a Run button next to it.

103

A checklist item configured with a nonexistent slash command does not have a Runbutton next to it

Continue from the above test.

1. Launch playbook backstage.

2. Find and click “Apb” to edit.

3. Add a new checklist item “C3” under “S1”.

4. Add slash command /invalidcommand for “C3”.

5. Save playbook.

6. Switch to normal channel view.

7. Start a new incident “Ia1” using “Apb”.

8. Once the incident has started, find “C3” under “S1”.

9. Verify that the slash command for “C3” doesn’t have a Run button next to it.

104

Clicking the Run button for a checklist slash command runs the slash command

Continue from the above test.

1. Open up the incident RHS for “Ia1”.

2. Find “C1” under stage “S1”.

3. Click the Run button next to “C1”.

4. Verify that clicking the Run button executes so that the status of user-1 is now set to “away”.

105

Plugin posts a message in the incident channel when a slash command Runis clicked

Continue from the above test.

1. Verify that plugin posts a message in the “Ia1” incident channel to notify that the slash command for “C1” has been run.

A message that the checklist item slash command was run (not the slash command system message)

106

Running a slash command with system message attached to it post the slash command system message in the incident channel

Continue from the above test.

1. Verify that the system message for the /away command “System: You are now away (Only visible to you)” is posted in the incident channel.

107

In case of two valid slash commands, the running the command from the checklist item will only run the first command successfully

Continue from the above test.

1. Launch playbook backstage.

2. Find and click “Apb” to edit.

3. Under “S1” add a new checklist item “C5”.

4. Add the following for “C5’s” slash command: /online /away.

5. Switch to normal channel view.

6. Start a new incident using “Apb”.

7. Once the incident has been started, find “C5” in the incident RHS.

8. Click the Run button next to “C5”.

9. Verify that the status of user-1 is now set to “online” and not “away”.

This is in sync with the core feature behavior

108

Running an invalid slash command from RHS checklist shows an ‘invalid slash command’ error

Depends on the steps in #102.

Like core feature?

109

A slash command can be run multiple times from the RHS checklist

Continue from the above tests.

1. Launch playbook backstage.

2. Find and click “Apb” to edit.

3. Under “S1” add a new checklist item “C6”.

4. Add /shrug as the slash command for “C6”.

5. Switch to normal channel view.

6. Start a new incident using “Apb”.

7. Once the incident has been started, find “C6” in the incident RHS.

8. Click the Run button for “C6”.

9. Verify that the /shrug command is executed successfully and a shrug message is posted in the center channel.

10. Repeat steps 8-9 multiple times.

110

A plugin post notifies when a slash command fails to run successfully

Verify that when a slash command fails to execute by clicking the Run button, the plugin posts a message in the center channel notifying that the execution has failed.

Test ID

Test Case

Test Steps

Result

Notes

111

Checklist item description

1. Create a playbook with checklist items that have markdown descriptions.

2. Start an incident using such playbook.

3. Make sure that hovering over the icon changes its opacity.

4. Verify that clicking on the icon opens up the popover.

5. Verify that the popover renders markdown correctly (included channel links and mentions).

6. Verify that clicking on the X icon closes the popover.

https://mattermost.atlassian.net/browse/MM-27016

112

Add pagination to playbook list

1. Navigate to backstage -> playbooks.

2. Create more than 16 playbooks.

3. Observe the pagination options at the bottom.

https://mattermost.atlassian.net/browse/MM-27344

113

Browse Playbook templates

1. Navigate to backstage > playbooks.

2. Click on any of the new templates.

https://mattermost.atlassian.net/browse/MM-27028

114

Channel link capability to the workflow markdown

A channel link in the checklist text (it has to be correct), such as ~town-square, should:

• be correctly highlighted like it is in the center channel

• be clickable and bring the user to that channel, /without/ refreshing the app.

https://mattermost.atlassian.net/browse/MM-26924

115

Test new playbook creation with Blank Playbook template

116

Test new playbook creation with Incident Response Playbook

117

Show workflow duration

1. Verify that total duration of the workflow is displayed in the RHS.

2. This value should update in realtime without requiring any refresh. Show days, hours, minutes and seconds as necessary.

https://mattermost.atlassian.net/browse/MM-27014

118

Return paginated response for all list endpoints

1. Make sure you can see multiple incident pages in backstage.

2. Make sure you can view existing playbooks.

https://mattermost.atlassian.net/browse/MM-26179

https://docs.google.com/document/d/1Kp2PmE8CDNUSUiviui4GhL51z5OmYf5QqrcxFu2YFJU/edit#heading=h.t5ecjz3pjyu3

119

Empty playbook landing

1. Open backstage.

2. Click playbooks.

3. Make sure no playbooks exists to see the empty state.

https://mattermost.atlassian.net/browse/MM-27027