Page Comparison

Test ID

Test Case

Test Steps

Result

Notes

89

A newly added checklist item in a playbook has a slash command field

1. Log in as user-1.

2. Launch playbook backstage.

3. Click “New Playbook”.

4. Enter “PB-N1” as the playbook name.

5. Under the preexisting “Default Stage”, click “Add new checklist item”.

6. Enter “I-1” as the checklist item name.

7. Hit enter.

8. Verify that two new fields, one for slash command, and the other for step description appear underneath.

9. Add more checklist items.

10. Verify that every new checklist item added has the slash command and step description fields.

90

A playbook can be edited to add a slash command to any checklist item

Continue from the above test.

1. Type /away in the slash command field for one of the checklist items.

2. Click “Save Playbook”.

3. Verify that the playbook is saved successfully.

4. Type other valid slash commands in the fields for other checklist items.

5. Verify that each slash command filed can successfully save the slash commands.

91

A checklist item configured with a slash command shows the slash command for that item in the RHS

Continue from the above tests.

1. Switch to a normal channel.

2. Start a new incident using “PB-N1”.

3. Open the incident RHS.

4. Verify that all checklist items configured with slash commands in the above tests, show the slash command under the checklist item.

92

A checklist item can only be configured with one slash command at most

1. Create a new playbook “P1a”.

2. Add a checklist item “C1”.

3. In the slash command field for “C1”, enter the following: /away /online /shrug.

4. Verify that a warning appears that the checklist item can only be configured with one slash command.

Valid?

93

Typing an invalid slash command

Test ID

Test Case

Test Steps

Result

Notes

94

Typing a / in the slash command field brings up a list of existing slash commands

1. Log in as user-1.

2. Launch playbooks backstage.

3. Click “New Playbook”.

4. Enter “PBa” as the playbook name.

5. Edit the name of the default stage to “S1”.

6. Click “Add new stage”.

7. Enter “C1” for checklist item name.

8. In the slash command field, enter /

9. Verify that a autocomplete list of all available slash commands pop up as soon as entering /.

95

Typing a non-/ character in the slash command field?

Should this be allowed?

96

Selecting from the slash command list auto completes the slash command

Continue from the above tests.

1. In the slash command field, enter /.

2. From the autocomplete list, click /dnd.

3. Verify that the slash command field is autocompleted with /dnd.

97

Typing a non-existing slash command shows a “invalid slash command” error

Valid?

98

The slash command field can be left empty

Continue from the above tests.

1. Remove the contents of “C1” so that the slash command field is empty.

2. Click “Save Playbook”.

3. Verify that the playbook is saved successfully.

Test ID

Test Case

Test Steps

Result

Notes

99

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

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

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

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

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

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

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

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

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

This is in sync with the core feature behavior

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

Like core feature?

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.

V

100

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.

101

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.

102

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.

103

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”.

104

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)

105

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.

106

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

107

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

Depends on the steps in #102.

Like core feature?

108

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.

109

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.