Test Plan - Incident Response v0.5

0.0

Initial version

05/14

0.1

Initial review from the team

06/15

1.0

Test run for 0.5 complete

07/24

1.1

Test doc cleaned up

07/27

Test ID

Test Case

Test Procedure

Result

Notes

1

Admin can install plugin in a non-EE instance

1. Log in to a non-enterprise Mattermost, as admin

2. From System Console > PLUGINS > Plugin Management, upload the Incident Response plugin.

3. Verify that the plugin can be installed.

2

Admin can install plugin in an E10 instance

1. Log in to Mattermost that has an E10 license, as admin.

2. From System Console > PLUGINS > Plugin Management, upload the Incident Response plugin.

3. Verify that the plugin is successfully installed.

3

Admin can install plugin in an E20 instance

1. Log in to Mattermost that has an E20 license, as admin

2. From System Console > PLUGINS > Plugin Management, upload the Incident Response plugin.

3. Verify that the plugin can be installed.

4

Admin can enable plugin

1. Once installed in the “Installed Plugins” section, find the Incident Response plugin v0.2.0 and click on the “Enable” button.

2. Verify that the plugin starts normally without errors.

5

Plugin functionality is available to admin

1. Switch to a normal channel.

2. Type /incidentin the post input box.

3. Verify that /incidentis listed as a slash command option.

4. Verify that the channel header has Incident Response icon for RHS.

5. Create a post.

6. Click post action menu for the post.

7. Verify that Start Incident is available as a post action menu option.

6

Plugin functionality is available to normal user

1. Log in as a non-admin user.

2. In a normal channel, type /incidentin the post input box.

3. Verify that /incidentis listed as a slash command option.

4. Verify that the channel header has Incident Response icon for RHS.

5. Create a post.

6. Click post action menu for the post.

7. Verify that Start Incident is available as a post action menu option.

7

Admin can disable plugin

1. Log out and log back in as admin.

2. From System Console > PLUGINS > Plugin Management, find the Incident Response plugin.

3. Click on the “Disable” button.

4. Verify that the plugin is disabled.

5. In the main channel’s post input box, type /incident.

6. Verify that /incident option is not present in the slash command list.

8

Admin can remove plugin

1. From System Console > PLUGINS > Plugin Management, find the Incident Response plugin.

2. Click on the “Remove” button.

3. Verify that the plugin is no longer installed in the instance.

9

Plugin upgrades normally from v0.3 to v0.5

1. Install version 0.3 of the plugin.

2. Upgrade to the latest version.

3. Verify that the plugin upgrade happens without any error.

10

Plugin upgrades normally from v0.4 to v0.5

1. Install version 0.4 of the plugin.

2. Upgrade to the latest version.

3. Verify that the plugin upgrade happens without any error.

11

Incidents started with the prior plugin versions are still active and available in v0.5

1. Start a few incident with plugin version 0.4.

2. Upgrade plugin to v0.5.

3. Open up the incident RHS to see the incident list.

4. Verify that incidents started with version 0.4 are still not available in v0.5.

 Not valid for upgrade to 0.5

12

Incidents ended with prior plugin versions are not available in v0.5

1. Start a few incident with plugin version 0.4.

2. Leave some as active and end a few of them.

3. Upgrade plugin to v0.5.

4. Open up the incident RHS to see the incident list.

5. Verify that incidents started with version 0.4 are still not available in v0.5.

6. Verify that incidents ended in step 2 are not visible in the list.

 Not valid for upgrade to 0.5

13

Playbook started with the older plugin version is still available upon plugin upgrade

1. Create a few playbooks with plugin version 0.4.

2. Upon plugin upgrade, verify that the playbooks created in step 1 are still not available in the backstage.

N/A

Not valid for upgrade to 0.5

Test ID

Test Case

Test Procedure

Result

Notes

14

Incident cannot be created without selecting a playbook

1. As user-1, bring up the incident creation modal.

2. Provide a channel name.

3. Do not select anything from the Playbook dropdown.

4. Do not input anything for Channel Name.

5. Click “Start Incident”.

6. Verify that incident is not created.

   1. Verify that the Incident Details modal remains open.

   2. Verify that “This field is required.” message appears below Playbook dropdown.

   3. Verify that “This field is required.” message appears below Channel Name input box.

7. Enter a Channel Name.

8. Leave the Playbook field empty.

9. Repeat steps 5 and 6.

15

User can make a public incident

1. As user-1, create a public playbook as follows:

   1. Launch the playbook backstage.

   2. Click “New Playbook”.

   3. Provide name of the playbook - “Public PB 1“.

   4. Enable the “Create Public Incident” option.

   5. Enter a few checklist items.

   6. Click “Save”.

2. Switch to the main channel view.

3. Create an incident by selecting the playbook “Public PB 1”.

4. Do not add any other user to the incident channel.

5. As user-2, verify that the incident is visible in the incident backstage.

6. Click on the incident.

7. Verify that the incident details can’t be viewed.

8. Verify that the incident details can be viewed.

#7 is a bug.

Fixed in master with https://github.com/mattermost/mattermost-plugin-incident-response/pull/219

16

User can make a private incident

1. As user-1, launch the playbook backstage.

2. Click “New Playbook”.

3. Provide a playbook name “Private-PB-1”.

4. Keep the “Create Public Incident” option disabled.

5. Add some checklist items.

6. Save playbook.

7. Create an incident by selecting the playbook “Private-PB-1”.

8. Log in as user-2.

9. Launch incident backstage.

10. Verify that the incident is not visible in the incident list.

17

Converting a public incident channel into private, makes the incident private

1. As a sysadmin, create a public incident “Pub-1”.

2. Log in as user-1.

3. Join the “Pub-1” incident channel to become a participant.

4. Convert it into a private incident

   1. Go to Pub-1 channel

   2. From the channel header, click the dropdown

   3. From the menu, select “Convert to Private Channel”

   4. In the “Convert public to a Private Channel” confirmation box, select “Yes..”

5. Verify access in backstage

   1. Launch incident backstage.

   2. Verify that the incident is visible in the incident list.

   3. Click on the incident.

   4. Verify that the incident details are accurately displayed.

18

Non participant cannot access a previously public incident converted to a private incident

Continue the test from above.

1. Log in as user-2.

2. Verify incident is not accessible in backstage.

   1. Launch incident backstage.

   2. Verify that the incident is not visible in the incident list.

19

Non participant cannot access a new private incident

1. As user-1, bring up the incident modal.

2. Give it the channel name “Pr-In-1”.

3. From the Playbook dropdown, select “Private-PB-1”.

4. Click “Start Incident”.

5. Do not add anyone else to the incident channel.

6. Log in as user-2.

7. Verify that the incident “Pr-In-1” is not visible in the incident RHS.

8. Launch incident backstage.

9. Verify that the incident “Pr-In-1” is not visible in the incident list.

20

Private incidents cannot be searched in backstage by non-participants.

Continue from the above test.

1. In the incident backstage, search for “Pub-1”.

2. Verify that “Pub-1” incident is not present in the search result.

3. Search for “Pr-In-1” in the backstage.

4. Verify that “Pr-In-1” incident is not present in the search result.

21

Public incidents are visible only within the incident’s team

1. As user-1, create a public incident in Team X.

2. Launch incident backstage.

3. Verify that the incident is visible in the incident list.

4. Switch to Team Y.

5. Launch the incident backstage.

6. Verify that the incident is not visible in the incident list.

7. As user-2, go to Team X.

8. Launch the incident backstage.

9. Verify that the incident is visible in the incident list.

10. Switch to Team Z.

11. Verify that the incident is not visible in the incident list.

22

Private incidents are visible only within the incident’s team

1. As user-1, create a private incident using playbook with private setting on.

2. Launch incident backstage.

3. Verify that the incident is visible in the incident list.

4. Switch to Team Y.

5. Launch the incident backstage.

6. Verify that the incident is not visible in the incident list.

7. As user-2, go to Team X.

8. Launch the incident backstage.

9. Verify that the incident is not visible in the incident list.

10. Switch to Team Z.

11. Verify that the incident is not visible in the incident list.

23

Public incidents cannot be searched in a different team’s incident backstage

1. As user-1, create a public incident “Pub C” in Team Y.

2. Launch incident backstage.

3. Verify that the incident is visible in the incident list.

4. Search for “Pub C” in the backstage.

5. Verify that “Pub C” is present in the search result.

6. Switch to Team X.

7. Launch the incident backstage.

8. Verify that the incident is not visible in the incident list.

9. Search for “Pub C” in the backstage.

10. Verify that “Pub C” is not present in the search result.

24

System administrator cannot see a private incident

1. As user-1, create a private incident “Pr A”.

2. Add a few checklist items.

3. Log in as sysadmin.

4. Launch incident backstage.

5. Verify that sysadmin cannot see “Pr A” in the incident list.

Won’t see private channel, but if permalink known, can simply browse to channel and self-join.

25

System administrator can join a private incident

Continue from the above test.

1. As sysadmin, use the permalink to the incident created in the above test.

2. Verify that sysadmin can successfully join the channel.

Won’t be in LHS, but definitely can join channel with permalink.

26

System administrator can view a private incident details

Continue from the above test.

1. As sysadmin, open up the incident RHS.

2. Verify that sysadmin can see the incident details for “Pr A” on the RHS.

3. Launch incident backstage.

4. Click on “Pr A”.

5. Verify that sysadmin can see the details of “Pr A” correctly in the details view in backstage.

27

System administrator can check and uncheck items in private incidents

Continue from the above test.

1. As sysadmin, open up the incident RHS to view the details of “Pr A”.

2. Check an item from the checklist.

3. Verify that sysadmin can successfully check an item off the list.

4. Uncheck an item from the checklist.

5. Verify that sysadmin can successfully uncheck an item off the list.

6. Launch the incident backstage.

7. Find and click “Pr A” to view the details.

8. Verify that the items checked off and unchecked are reflected properly in the graph.

28

System administrator can end a private incident

Continue from the above test.

1. As sysadmin, open the incident details of “Pr A” on the RHS.

2. Click “End Incident”.

3. Verify that the incident is ended successfully.

4. Launch the incident backstage.

5. Verify that the incident end state under “Status” is properly reflected in the list view.

6. Verify that the incident end state is properly reflected in the incident details view.

29

Team administrator cannot see a private incident

1. As user-1, create a private incident “Pr B”.

2. Add checklist items “check 1” and “check 2”.

3. Log in as a team admin.

4. Verify that team admin cannot see the private channel “Pr B” on the LHS.

5. Launch incident backstage.

6. Verify that team admin cannot see “Pr B” in the incident list.

Team admins can’t see a private incident. Test changed from can to cannot.

30

Team administrator can check and uncheck items in private incidents

Continue from the above test.

1. Invite team admin to the “Pr B” incident channel.

2. As team admin, open up the incident RHS to view the details of “Pr B”.

3. Check both items “check 1” and “check 2” from the checklist.

4. Verify that team admin can successfully check the item off the list.

5. Uncheck item “check 2” from the checklist.

6. Verify that team admin can successfully uncheck the item off the list.

7. Launch the incident backstage.

8. Find and click “Pr B” to view the details.

9. Verify that the items checked off and unchecked are reflected properly in the graph.

Team admins can’t see a private incident. Invalid test.

31

Team administrator can end a private incident

Continue from the above test.

1. As team admin, open the incident details of “Pr B” on the RHS.

2. Click “End Incident”.

3. Verify that the incident is ended successfully.

4. Launch the incident backstage.

5. Verify that the incident end state under “Status” is properly reflected in the list view.

6. Verify that the incident end state is properly reflected in the incident details view.

Test ID

Test Case

Test Procedure

Result

Notes

32

Playbook can be configured to create a public incident

1. Log in as team admin.

2. Launch playbook backstage.

3. Click on “New Playbook”.

4. Enter “PB 1” for Playbook Name.

5. Enable the button to “Create Public Incident”.

6. Add checklist items “item 1” , “item 2” and “item 3”.

7. Click “Save Playbook”.

8. Switch to normal channel view.

9. Bring up the incident creation dialog.

10. Create incident “New Public PB1”.

11. From the playbook dropdown, select “PB 1”.

12. Click “Start Incident”.

13. Verify that the incident created has the correct checklist items.

14. Log in as user-2.

15. Launch incident backstage.

16. Verify user-2 can see “New Public PB1” in the incident list.

33

Playbook can be configured to create a private incident

1. Log in as team admin.

2. Launch playbook backstage.

3. Click on “New Playbook”.

4. Enter “PB 2” for Playbook Name.

5. Ensure the button to “Create Public Incident” is disabled.

6. Add checklist items “item a” , “item b” and “item c”.

7. Click “Save Playbook”.

8. Switch to normal channel view.

9. Bring up the incident creation dialog.

10. Create incident “New Public PB2”.

11. From the playbook dropdown, select “PB 2”.

12. Click “Start Incident”.

13. Verify that the incident created has the correct checklist items.

14. Log in as user-2.

15. Launch incident backstage.

16. Verify user-2 cannot see “New Public PB1” in the incident list.

34

Playbook can be edited to change public incident creation setting to private

Continue from the above tests.

1. Log in as user-1.

2. Launch playbook backstage.

3. Find playbook “PB 1”.

4. Click “Edit”.

5. Disable the button to “Create Public Incident”.

6. Click “Save Playbook”.

7. Switch to normal channel view.

8. Bring up the incident creation dialog.

9. Create incident “Incident PB3”.

10. From the playbook dropdown, select “PB 1”.

11. Click “Start Incident”.

12. Verify that the incident created has the correct checklist items.

13. Log in as user-2.

14. Launch incident backstage.

15. Verify user-2 cannot see “Incident PB3” in the incident list.

35

Playbook can be edited to change private incident creation setting to public

Continue from the above tests.

1. Log in as user-1.

2. Launch playbook backstage.

3. Find playbook “PB 2”.

4. Click “Edit”.

5. Enable the button to “Create Public Incident”.

6. Click “Save Playbook”.

7. Switch to normal channel view.

8. Bring up the incident creation dialog.

9. Create incident “Incident PB4”.

10. From the playbook dropdown, select “PB 2”.

11. Click “Start Incident”.

12. Verify that the incident created has the correct checklist items.

13. Log in as user-2.

14. Launch incident backstage.

15. Verify user-2 can see “Incident PB4” in the incident list.

Test ID

Test Case

Test Procedure

Result

Notes

36

Incidents in backstage will be listed in priority order

1. Log in as user-1.

2. Add user-2 to incident “New Public PB 1”.

3. Log in as user-2.

4. Create a private incident “U2 Pr 1”.

5. Launch incident backstage.

6. Verify that the incidents are listed in the following order:

   1. U2 Pr 1 (user-2 is the creator)

   2. New Public PB 1 (user-2 is the member of)

   3. Incident PB4 (public incident that user-2 is not a member of)

7. Switch to a normal channel view.

8. Create a new public incident “U2 Pu”.

9. Launch incident backstage.

10. Verify that the incidents are listed in the following order:

    1. U2 Pu (the latest incident created by user-2)

    2. U2 Pr 1

    3. New Public PB 1

    4. Incident PB 4

N/A

Is the order correct in step 6 and 10?

Prioritizing incident was for RHS incident list. Since incident list is removed from the RHS, this test is invalid.

Test ID

Test Case

Test Procedure

Result

Notes

37

System administrator can create a public incident playbook

1. Log in as a sysadmin.

2. Launch the Playbooks backstage (either from main menu or incident RHS header’s playbook button).

3. Click “New Playbook”.

4. Enable the setting for “Create Public Playbook”.

5. Provide “SA PB 1” for the Playbook Name.

6. Enable the setting for “Create Public Incident” to allow the playbook to create public incidents by default.

7. Add the following checklist items:

   1. Start test

   2. Edit test

   3. End test

8. Click “Save Playbook”.

9. Verify that upon saving, “SA PB 1” exists in the playbook list view in backstage.

38

System administrator can create a private incident playbook

1. Log in as a sysadmin.

2. Launch the Playbooks backstage (either from main menu or incident RHS header’s playbook button).

3. Click “New Playbook”.

4. Enable the setting for “Create Public Playbook”.

5. Provide “SA PB 2” for the Playbook Name.

6. Disable the setting for “Create Public Incident” to allow the playbook to create private incidents by default.

7. Add the following checklist items:

   1. Start test

   2. Edit test

   3. End test

8. Click “Save Playbook”.

9. Verify that upon saving, “SA PB 2” exists in the playbook list view in backstage.

39

Team admin can create a public-incident playbook

1. Log in as a team admin.

2. Launch the Playbooks backstage (either from main menu or incident RHS header’s playbook button).

3. Click “New Playbook”.

4. Ensure the “Create Public Incident” setting is enabled.

5. Provide “TA PB 3” for the Playbook Name.

6. Enable the setting for “Create Public Incident” to allow the playbook to create public incidents by default.

7. Add the following checklist items:

   1. Start test

   2. Edit test

   3. End test

8. Click “Save Playbook”.

9. Verify that upon saving, “TA PB 3” exists in the playbook list view in backstage.

40

Team admin can create a private-incident playbook

1. Log in as a team admin.

2. Launch the Playbooks backstage (either from main menu or incident RHS header’s playbook button).

3. Click “New Playbook”.

4. Ensure the “Create Public Playbook” setting is disabled.

5. Provide “TA PB 4” for the Playbook Name.

6. Disable the setting for “Create Public Incident” to allow the playbook to create private incidents by default.

7. Add the following checklist items:

   1. Start test

   2. Edit test

   3. End test

8. Click “Save Playbook”.

9. Verify that upon saving, “TA PB 4” exists in the playbook list view in backstage.

41

A playbook is initially only visible to playbook creator

1. Log in as user-1.

2. Launch playbook backstage.

3. Create a new playbook “U1PB”.

4. Verify that “Members” has only user-1 included.

5. Switch to a normal channel view.

6. Bring up the incident creation dialog.

7. Verify that user-1 can see “U1PB” listed in the playbook dropdown.

8. Log in as user-2.

9. Launch playbook backstage.

10. Verify that user-2 does not see “U1PB” in the Playbooks list.

11. Switch to a normal channel view.

12. Bring up the incident creation dialog.

13. Verify that user-2 cannot see “U1PB” listed in the playbook dropdown.

42

Private playbook cannot be deleted by non-participating member user of the team

Continue from the above test.

1. Log in as user-1.

2. Issue a DELETE request to http://localhost:8065/plugins/com.mattermost.plugin-incident-response/api/v1/playbooks/[playbook-id].

3. Verify that the request cannot be completed.

4. As team admin, verify that the playbook did not get deleted.

Test ID

Test Case

Test Procedure

Result

Notes

43

Users who have access to a playbook limit playbook access to specific users

1. Log in as team admin.

2. Create a playbook “TA 1”.

3. Add checklist items “1”, “2” and “3”.

4. Invite user-2 in the playbook.

5. Click “Save Playbook”.

6. Login as user-1.

7. Launch playbook backstage.

8. Verify that user-1 cannot find “TA 1” in the backstage.

9. Switch to normal channel view.

10. Bring up the incident creation dialog.

11. Verify that user-1 cannot find “TA 1” in the playbook dropdown.

12. Login as user-2.

13. Launch playbook backstage.

14. Verify that user-1 can find “TA 1” in the backstage.

15. Switch to normal channel view.

16. Bring up the incident creation dialog.

17. Verify that user-1 can find “TA 1” in the playbook dropdown.

44

Playbook member can edit users who have access to playbook

Continue from the above test.

1. As team admin, launch playbook backstage.

2. Find “TA 1”.

3. Click “Edit”.

4. Invite user-1 to manage the playbook “TA 1”.

5. Click “Save Playbook”.

6. Verify that user-1 can now find “TA 1” in the backstage.

7. Switch to normal channel view.

8. Bring up the incident creation dialog.

9. Verify that user-1 can now find “TA 1” in the playbook dropdown.

45

User removed by a playbook member can no longer access playbook

Continue from the above test.

1. As user-1, launch playbook backstage.

2. Find “TA 1”.

3. Click “Edit”.

4. Remove team admin from the playbook “TA 1”.

5. Click “Save Playbook”.

6. Verify that user-2 cannot find “TA 1” in the backstage.

7. Switch to normal channel view.

8. Bring up the incident creation dialog.

9. Verify that team admin cannot find “TA 1” in the playbook dropdown.

46

Playbook member can limit playbook access to specific users

1. Log in as team admin.

2. Create a playbook “Sa 1”.

3. Add checklist items “a”, “b” and “c”.

4. Invite user-2 in the playbook.

5. Click “Save Playbook”.

6. Login as user-1.

7. Launch playbook backstage.

8. Verify that user-1 cannot find “Sa 1” in the backstage.

9. Switch to normal channel view.

10. Bring up the incident creation dialog.

11. Verify that user-1 cannot find “Sa 1” in the playbook dropdown.

12. Login as user-2.

13. Launch playbook backstage.

14. Verify that user-2 can find “Sa 1” in the backstage.

15. Switch to normal channel view.

16. Bring up the incident creation dialog.

17. Verify that user-2 can find “Sa 1” in the playbook dropdown.

47

Playbook member can edit users who have access to playbook

Continue from the above test.

1. As team admin, launch playbook backstage.

2. Find “Sa 1”.

3. Click “Edit”.

4. Invite user-1 to manage the playbook “Sa 1”.

5. Click “Save Playbook”.

6. Verify that user-1 can now find “Sa 1” in the backstage.

7. Switch to normal channel view.

8. Bring up the incident creation dialog.

9. Verify that user-1 can now find “Sa 1” in the playbook dropdown.

48

User removed by system admin can no longer access playbook

Continue from the above test.

1. As team admin, launch playbook backstage.

2. Find “Sa 1”.

3. Click “Edit”.

4. Remove user-2 from the playbook “Sa 1”.

5. Click “Save Playbook”.

6. Verify that user-2 cannot find “Sa 1” in the backstage.

7. Switch to normal channel view.

8. Bring up the incident creation dialog.

9. Verify that user-2 cannot find “Sa 1” in the playbook dropdown.

49

Last playbook member cannot be removed from the playbook

1. Log in as user-1.

2. Create a playbook.

3. Add user-2 as a member to the playbook.

4. Log in as user-2.

5. Verify that user-2 can access the playbook in the backstage.

6. Go to the editing view of the playbook.

7. Remove user-1 from the playbook.

8. Save the playbook.

9. Verify that the playbook saved successfully.

10. Go back to the editing view of the playbook.

11. Remove the user themself (user-2) as the member.

12. Click “Save Playbook”.

13. Verify taht the playbook cannot be saved.

Test ID

Test Case

Test Procedure

Result

Notes

50

Test UI in light theme

1. Test UI in light theme in Chrome.

2. Test UI in light theme in Firefox.

3. Test UI in light theme in Safari.

4. Test UI in light theme in Desktop app.

5. Spot check in mobile app.

6. Spot check in mobile browser.

51

Test UI in dark theme

1. Test UI in dark theme in Chrome.

2. Test UI in dark theme in Firefox.

3. Test UI in dark theme in Safari.

4. Test UI in dark theme in Desktop app.

5. Spot check in mobile app.

6. Spot check in mobile browser.

Done

Bugs filed for dark themes.

52

Test UI in Monokai theme

1. Test UI in Monokai theme in Chrome.

2. Test UI in Monokai theme in Firefox.

3. Test UI in Monokai theme in Safari.

4. Test UI in Monokai theme in Desktop app.

5. Spot check in mobile app.

6. Spot check in mobile browser.{"sidebarBg":"#2f3136","sidebarText":"#8f9297","sidebarUnreadText":"#dcddde","sidebarTextHoverBg":"#35363c","sidebarTextActiveBorder":"#35363c","sidebarTextActiveColor":"#dcddde","sidebarHeaderBg":"#282b30","sidebarHeaderTextColor":"#818386","onlineIndicator":"#64b285","awayIndicator":"#eea941","dndIndicator":"#b74b47","mentionBg":"#7289da","mentionBj":"#ffffff","mentionColor":"#dcddde","centerChannelBg":"#36393e","centerChannelColor":"#dcddde","newMessageSeparator":"#f75252","linkColor":"#7289da","buttonBg":"#43b581","buttonColor":"#ffffff","errorTextColor":"#fd5960","mentionHighlightBg":"#36393e","mentionHighlightLink":"#7289da","codeTheme":"monokai"}

Done

Bugs filed

Test ID

Test Case

Test Procedure

Result

Tickets

Notes

53

Channel is archived when ending an incident with slash command

1. Set ExperimentalViewArchivedChannels to true or, from System Console > Site Configuration > User and Teams, set “Allow users to view archived channels” to true.

2. Start a new incident using any method.

3. Locate the channel in the LHS.

4. End the incident using the /incident end command.

5. Click “Confirm” in the confirmation dialog.

6. Verify that the incident ended.

   1. Status of the incident changed to “Ended” in the backstage.

7. Verify that the incident channel is archived:

   1. In the LHS, verify the incident channel is listed with the archived icon.

   2. Running CLI command ./mattermost channel list [team-name] shows the channel as '(archived)'.

N/A

Moved from 0.5

Ticket is still open: https://mattermost.atlassian.net/browse/MM-24408

54

Channel is archived when ending an incident from RHS

1. Start a new incident using any method.

2. Locate the channel in the LHS.

3. End the incident from the RHS.

4. Click “Confirm” in the confirmation dialog.

5. Verify that the incident ended.

   1. Incident no longer appears in the RHS list.

   2. Status of the incident changed to “Ended” in the backstage.

6. Verify that the incident channel is archived:

   1. In the LHS, verify the incident channel is listed with the archived icon.

   2. Running CLI command ./mattermost channel list [team-name] shows the channel as '(archived)'.

N/A

Moved from 0.5

55

The incident channel shows up under archived channel once the incident is ended

1. On the LHS click “more” under Private Channels.

2. Ensure “Show: Archived Channels” is selected in the dropdown.

3. Verify the channels of the incidents ended in the above 2 tests are listed.

N/A

Moved from 0.5

56

Incident channels do not appear in LHS when archived channel display is turned off

1. Set ExperimentalViewArchivedChannels to false or, from System Console > Site Configuration > User and Teams, set “Allow users to view archived channels” to false.

2. Switch to normal channel view.

3. Verify that the channels of the incidents ended in the tests above do not appear on the LHS.

N/A

Moved from 0.5

57

Add a message indicating no checklist items in Incidents RHS

 N/A

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

Moved from 0.4

Ticket closed as won’t fix.

58

Support incident list pagination

1. Create a new team so that there are no incidents.

2. Create 24 incidents.

3. Launch the incident backstage.

   1. From the channel header, click the incident icon.

   2. In the incident RHS, click the playbook icon to launch the backstage.

   3. Click the “Incidents” tab on the LHS.

4. Verify that all 24 incidents created in step 2 are displayed in the list on the same page.

5. Verify there is no “Next” and “Previous” buttons at the bottom of the page.

6. Create one more incident so that the total number of incidents are 25.

7. In the incident backstage, verify that all 25 incidents are displayed in the same page.

8. Verify there is no “Next” and “Previous” buttons at the bottom of the page.

9. Create one more incident so that the total number of incidents are now 26.

10. In the incident backstage, scroll to the bottom of the page.

11. Verify there are 25 incidents displayed on the first incident list page.

12. Verify there is no “Previous” button.

13. Verify there is a “Next” button.

14. Click on the “Next” button.

15. Verify that page 2 of the incident lists page loads.

16. Verify that there is only 1 incident in the 2nd page.

17. Verify there is “Previous” button in the 2nd page.

18. Create incidents so that there are now a total of 51 incidents.

19. In the 2nd page of the incident list page in the backstage, verify there is “Previous” button and a “Next” button.

20. Verify both “Previous” and “Next” button are functional.

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

Moved from 0.4

59

Support incident list sorting on End Date

1. Create a few incidents at varying times.

2. Launch the incident backstage to view the incident list.

3. Verify that incidents are listed with the newest one on top by default.

4. Click “End Date” in the header.

5. Verify that the incident list is rearranged such that the last one that was ended is now at the top of the list, followed by other ‘Ended’ incidents in descending order of the time the incidents were ended, followed by the ‘Ongoing’ incidents (descending order of creation?)

6. Verify that all other incident info are still associated with the incidents correctly.

7. Click “End Date” again.

8. Verify that the incident list is rearranged such that the first incident to end is now at the top of the list, followed by other ‘Ended’ incidents in ascending order of the time the incidents were ended, followed by the ‘Ongoing’ incidents (ascending order of creation?).

9. Verify that all other incident info are still associated with the incidents correctly.

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

Moved from 0.4

60

Support incident list sorting on Start Date

Continue from the test for “Support incident list sorting on End Date”

1. Click “Start Date” in the header.

2. Verify that the incident list is rearranged such that the first incident to get created is now at the top of the list, followed by other incidents (ongoing or ended) in ascending order of the time the incidents were created.

3. Verify that all other incident info are still associated with the incidents correctly.

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

Moved from 0.4

61

“Create a playbook” link in Incident Details modal links to New Playbook page in backstage