Versions Compared

Version Old Version 10 New Version 11
Changes made by

Prapti Shrestha

Prapti Shrestha

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Document version 1.0

Status: v0.5 test in progress…

...

Test Server (upgrade tests): https://ir-upgrade-test.test.mattermost.cloud

Build Hash: ed34468996e6906003c9b3cab0d21ac121ec553f
EE Build Hash: 9547727aa1779259a9dcd847c81e4c29a0db0845
Webapp Build Hash: b8a75b515bd4646d2084da2c72d12588b233ded5

...

         

Test Area - Plugin Setup

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.

 Pass

 

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.

 Pass

 

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.

 Pass

 

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.

 Pass

 

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.

 Pass

 

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.

 Pass

 

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.

 Pass

 

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.

 Pass

 

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.

 Pass

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.

 Pass

 

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.

Not valid for upgrade to 0.5

Test Area - Limit incident access to only participants

As an incident participant, I can make an incident and its channel private so that non-participants don’t know it exists let alone access its content.

Test ID

Test Case

Test Procedure

Result

Notes

14

Incident created without selecting a playbook is public by default

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.

#7 is a bug.

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. Verify that the incident is not visible in the incident RHS.

  10. Launch incident backstage.

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

#9: RHS incident list may go away.

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

Non participants can view public incident details in RHS

Continue from the above test.

  1. As user-1, add checklist items to Pub C.

  2. Check at least 1 item on the checklist.

  3. As user-2 go to Team Y.

  4. From the public channels list in the LHS, find the incident channel for “Pub C” and click.

  5. Verify that the Pub C incident details view opens up in the RHS.

  6. Verify that user-2 can see the checklist items as created in step 1.

  7. Verify that user-2 can see the correct state of checklist items as modified in step 2.

Invalid - user has to be added to the IR channel to be able to launch anything about the incident in the RHS.

25

Non participants cannot edit incident details in RHS of a public incident unless added as the incident channel’s member

Continue from the above test.

  1. As user 2, go to Team Y.

  2. View Pub C’s details on the RHS.

  3. Verify that the checklist items are greyed out (inactive).

  4. Verify user-2 cannot add items to the checklist.

  5. Verify user-2 cannot check off checklist items.

  6. Verify user-2 cannot uncheck checklist items.

Need to find out more about the mechanism to view the incident details on RHS if the details view is going to be tightly coupled with the channel view.

26

Non participant cannot view private incident details in RHS

Is this test case correct? Non-participant can’t see private channels.

27

System administrator can 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. Verify that sysadmin can see the private channel “Pr A” on the LHS.

  5. Launch incident backstage.

  6. Verify that sysadmin can see “Pr A” in the incident list.

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

28

System administrator can join a private incident

Continue from the above test.

  1. As sysadmin, in the main channel view, find and click “Pr A” on the LHS.

  2. Verify that sysadmin can successfully join the channel.

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

29

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.

30

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.

31

System administrator can add and remove checklist items in a private incident

Continue from the above test.

  1. As sysadmin, add checklist item “Admin check“ to “Pr A”.

  2. Verify that “Admin check” is successfully added to the checklist.

  3. Remove one of the items added earlier by user-1 from the checklist.

  4. Verify that the item is successfully removed.

  5. Launch the incident backstage.

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

  7. Verify that the items added and removed are reflected properly.

32

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.

33

Team administrator can 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 can see the private channel “Pr B” on the LHS.

  5. Launch incident backstage.

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

34

Team administrator can join a private incident

Continue from the above test.

  1. As team admin, in the main channel view, find and click “Pr B” on the LHS.

  2. Verify that team admin can successfully join the channel.

35

Team administrator can view a private incident details

Continue from the above test.

  1. As team admin, open up the incident RHS.

  2. Verify that team admin can see the incident details for “Pr B” on the RHS.

  3. Launch incident backstage.

  4. Click on “Pr B.

  5. Verify that team admin can see the details of “Pr B” correctly in the details view in backstage.

36

Team administrator can check and uncheck items in private incidents

Continue from the above test.

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

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

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

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

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

  6. Launch the incident backstage.

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

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

37

Team administrator can add and remove checklist items in a private incident

Continue from the above test.

  1. As team admin, add checklist item “check 3“ to “Pr B”.

  2. Verify that “check 3” is successfully added to the checklist.

  3. Remove “check 2” from the checklist.

  4. Verify that the item is successfully removed.

  5. Launch the incident backstage.

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

  7. Verify that the items added and removed are reflected properly.

38

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 Area - Configure playbooks to create public/private incidents

As an incident manager, I can configure playbooks to create either public or private incidents so that it defaults to the correct permission when executed.

Test ID

Test Case

Test Procedure

Result

Notes

39

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.

40

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.

41

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.

42

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 Area - Prioritize incidents that the user is a participant of

As an incident participant, I can easily tell apart the incidents that are relevant to me so that it’s I can get there more quickly.

Test ID

Test Case

Test Procedure

Result

Notes

43

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

Is the order correct in step 6 and 10?

Effect of search on priority ordering in backstage

Effect of sorting on priority ordering in backstage

Effect on LHS channel order for priority ordering

Test Area - Limit the ability to create playbooks to Team Administrators

As a system administrator, I can restrict who can create playbooks so that the incident response process can be better standardized.

Test ID

Test Case

Test Procedure

Result

Notes

44

System administrator can create a public 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.

Is step #4 correct?

45

System administrator can create a private 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.

#4 correct?

46

Team admin can create a public 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. Enable the setting for “Create Public Playbook”.

  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.

#4 correct?

47

Team admin can create a private 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. Enable the setting for “Create Public Playbook”.

  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.

#4 correct?

48

A non-admin user cannot create a playbook

  1. Log in as a non-admin user.

  2. Launch playbooks backstage.

  3. Verify that there is no “New Playbook” button in the playbooks backstage.

Is #3 correct?

49

A non-admin user cannot create a private playbook

N/A due to the test above this one. Is this correct?

50

Private playbook is initially only visible to playbook creator

  1. Log in as a non-admin user.

  2. Launch playbooks backstage.

  3. Verify that playbooks “SA PB 2” and “TA PB 4” are not visible in the backstage.

  4. Switch to a normal channel view.

  5. Bring up the incident creation dialog.

  6. Verify that playbooks “SA PB 2” and “TA PB 4” are not available in the Playbook dropdown.

  7. Log in as the team admin.

  8. Launch Playbooks backstage.

  9. Verify that “SA PB 2” is not visible in the backstage.

  10. Switch to normal channel view.

  11. Bring up the incident creation dialog.

  12. Verify that “SA PB 2” is not available in the Playbook dropdown.

  13. Log in as the sysadmin.

  14. Launch Playbooks backstage.

  15. Verify that “TA PB 4” is not visible in the backstage.

  16. Switch to normal channel view.

  17. Bring up the incident creation dialog.

  18. Verify that “TA PB 4” is not available in the Playbook backstage.

Are steps 13-18 correct?

Are private playbooks visible to/accessible by system admins? Or do they need to be invited to the playbook to access them as well?

51

Private playbook is only available within the team it was created in

  1. Log in as sysadmin.

  2. Switch to different team than the one where “SA PB 1” and “SA PB 2” were created.

  3. Launch the Playbook backstage.

  4. Verify that the playbooks “SA PB 1” and “SA PB 2” are not visible in the backstage.

  5. Switch to normal channel view.

  6. Bring up the incident creation dialog.

  7. Verify that “SA PB 1” and “SA PB 2” are not available in the Playbook backstage.

52

Public playbook is visible to all the members of a team

  1. Create a new team “Team B”.

  2. Don’t add any user to the team.

  3. Create a public playbook - “Pub-PB1”.

  4. Verify no other user (non-admin team member, guest) can see “Pub-PB1” in backstage since they are not added to Team B”.

  5. Add user-1 to Team B.

  6. Log in as user-1.

  7. Verify that user-1 can see “Pub-PB1” in backstage.

  8. Verify that user-1 can see “Pub-PB1” in incident creation dialog’s playbook dropdown.

  9. Add user-2 to Team B.

  10. Create a new public playbook - “Pub-PB2”.

  11. Verify that both user-1 and user-2 can see “Pub-PB2” in backstage.

  12. Verify that both user-1 and user-2 can see “Pub-PB2” in incident creation dialog’s playbook dropdown.

53

Public playbook can be edited by member user of the team

Continue from the above tests.

  1. Log in as user-1.

  2. In Team B, launch the Playbook backstage.

  3. Find the playbook “Pub-PB2”.

  4. Click Edit for the playbook.

  5. Enable the setting for “Create Public Incident”.

  6. Add item “new task”.

  7. Click “Save Playbook”.

  8. Verify that the edit has been saved properly.

  9. Click “Edit” again.

  10. Verify that the edits made in step 5 & 6 persisted.

54

Team member can “invite” other team members to manage public playbook

Not sure about steps to invite other members to manage playbook.

55

Team member can create an incident using public playbook

Continue from the above test.

  1. Log in as user-2.

  2. Bring up the incident creation modal.

  3. Create a new incident with playbook “Pub-PB2”.

  4. Open the incident details.

  5. Verify that the incident created is a public incident.

  6. Verify that the incident created has all settings and checklist items as edited in the above test.

56

Public playbook can be deleted by team member

  1. Log in as user-2.

  2. Launch Playbook backstage.

  3. Find “Pub-PB2”.

  4. Click “Delete” for the playbook.

  5. Click “Delete Playbook” in the confirmation modal.

  6. Verify that the playbook is gone from the backstage list view.

  7. Switch to normal channel view.

  8. Bring up the incident creation modal.

  9. Verify that “Pub-PB2” is not available in the playbook dropdown.

57

Private playbook cannot be edited by a non-admin team member

  1. Note the playbook name and playbook-id of the private playbook “TA SB 4”

  2. Log in as user-1.

  3. Issue a PUT request to http://localhost:8065/plugins/com.mattermost.plugin-incident-response/api/v1/playbooks/[playbook-id]` with a payload change to add a checklist item.

  4. Verify that the request cannot be completed.

  5. As team admin, verify that the PUT request made in 3 did not take effect.

Using a direct PUT to test here because the user will not be able to find the private playbook in the UI.

58

Private playbook cannot be deleted by 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.

59

Non-admin team member cannot “invite” other team members to manage private playbook

Continue from the above test.

  1. Log in as team admin.

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

  3. Log in as user-1.

  4. Verify that user-1 can edit the playbook.

  5. As user-1 try inviting user-2 to manage the playbook.

  6. Verify that user-1 cannot invite user-2 to manage the playbook.

60

Non-admin team member cannot create an incident using private playbook if not invited to manage the playbook

Covered by #45

Test Area - Limit playbook access to specific users

As a playbook creator, I can specify who else can see and edit the playbook so that sensitive content wouldn’t be unintentionally revealed.

Test ID

Test Case

Test Procedure

Result

Notes

61

Team admin can 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.

62

Team admin 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.

63

User removed by team admin can no longer access playbook

Continue from the above test.

  1. As team admin, launch playbook backstage.

  2. Find “TA 1”.

  3. Click “Edit”.

  4. Remove user-2 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 user-2 cannot find “TA 1” in the playbook dropdown.

64

System admin 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-1 can find “Sa 1” in the backstage.

  15. Switch to normal channel view.

  16. Bring up the incident creation dialog.

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

65

System admin 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.

66

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.

...