Test Area (v0.7) - Attach a slash command to each step when editing playbook |
|---|
Test ID | Test Case | Test Steps | Result | Notes |
| A newly added checklist item in a playbook has a slash command field | A playbook can be edited to add a slash command to any checklist item | A checklist item configured with a slash command shows the slash command for that item in the RHS | | Log in as user-1. Launch playbook backstage. Click “New Playbook”. Enter “PB-N1” as the playbook name. Under the preexisting “Default Stage”, click “Add new checklist item”. Enter “I-1” as the checklist item name. Hit enter. Verify that two new fields, one for slash command, and the other for step description appear underneath. Add more checklist items. Verify that every new checklist item added has the slash command and step description fields.
| | |
| A playbook can be edited to add a slash command to any checklist item | Continue from the above test. Type /away in the slash command field for one of the checklist items. Click “Save Playbook”. Verify that the playbook is saved successfully. Type other valid slash commands in the fields for other checklist items. Verify that each slash command filed can successfully save the slash commands.
| | |
| A checklist item configured with a slash command shows the slash command for that item in the RHS | Continue from the above tests. Switch to a normal channel. Start a new incident using “PB-N1”. Open the incident RHS. Verify that all checklist items configured with slash commands in the above tests, show the slash command under the checklist item.
| | |
| A checklist item can only be configured with one slash command at most | Create a new playbook “P1a”. Add a checklist item “C1”. In the slash command field for “C1”, enter the following: /away /online /shrug. Verify that a warning appears that the checklist item can only be configured with one slash command.
| | Valid? |
| Typing an invalid slash command | | | |