Versions Compared

Key

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

...

...

Document version 0.

...

1

Status: Test plan development in progress

Document Version

Description

Date

0.0

Initial version

04/14

0.1

  • Updated to reflect response from the sync-up on 04/16

  • Removed tests for v0.3.0

04/16

Summary

This document details the tests for Incident Response plugin v0.2.0. The tests are derived from the user stories in Incident Responseoverview.

...

Test Area - Coordinate

Test ID

Test Case

Test Procedure

Result

Notes

28

Commander can check off items in incident checklist

  1. Start an incident.

  2. Create a checklist with a few items.

  3. Verify that the commander can check items off.

29

Commander can uncheck items in incident checklist

  1. Start an incident.

  2. Create a checklist with a few items.

  3. Check off the items.

  4. Verify that the commander can uncheck items.

30

Non-commander who is not added to incident channel cannot check off items in incident checklist

  1. Start an incident as user A.

  2. Create a checklist with a few items.

  3. Log in as user B.

  4. Verify that user B cannot check off items in step 2.

31

Non-commander who is not added to incident channel cannot uncheck items in incident checklist

  1. Start an incident as user A.

  2. Create a checklist with a few items.

  3. Check off a few items in the list.

  4. Log in as user B.

  5. Verify that user B cannot uncheck items in step 3.

32

Non-commander user, who is added to the incident channel, can check off items in incident checklist

  1. Start an incident as user A.

  2. Create a checklist with a few items.

  3. Add user B to the incident channel.

  4. Verify that user B can check items off.

33

Non-commander user, who is added to the incident channel, can uncheck items

  1. Start an incident as user A.

  2. Create a checklist with a few items.

  3. Add user B to the incident channel.

  4. Verify that user B can check off items added in step 3.

  5. Verify that user B can uncheck items checked off in step 4.

34

Non-commander user, who is added to the incident channel, can uncheck items checked off by the commander

  1. Start an incident as user A.

  2. Create a checklist with a few items.

  3. Check items on the list.

  4. Add user B to the incident channel.

  5. Verify that user B can uncheck items that were checked off in step 3.

35

Non-commander cannot end incident from RHS

As user A start

Ending an incident shows a confirmation modal

  1. Start an incident.As user B

  2. , verify that the incident is visible in RHSOpen the RHS and find the incident just started.

  3. Click the incident to view details.

  4. Verify that there is no an “End Incident” button at the bottom.

  5. Click on the button.

  6. As user A, add user B to the incident channel.

  7. As user B, navigate Verify a confirmation modal pops up asking whether to end the incident.

  8. Go to the incident channel.

  9. In the RHS, find the incident and click to view details.

  10. Verify there is no “End Incident” button.

Fix from 0
  1. post input box type /incident end

  2. Verify a confirmation modal pops up asking whether to end the incident.

36

Commander can end incident

Continue from the above test:

  1. Click to confirm ending the incident.

  2. Verify that the incident is ended.

(Incident end verifications in Test Plan - Incident Response v0.1.0 )

3637

Non-commander cannot can end incident with /incident command.from RHS

  1. As user A start an incident.

  2. As user B, verify that the incident is visible in RHS.

  3. Navigate to any channel.

  4. In the post input box, type `/incident'Click the incident to view details.

  5. Verify that there is no /incidentoption present in the slash commands“End Incident” button.

  6. As user A, add user B to the incident channel.

  7. As user B, navigate to the incident channel.

  8. In the post input box, type `/incident'RHS, find the incident and click to view details.

  9. Verify that there is no /incidentoption present in the slash commands.

37
  1. “End Incident” button.

  2. Click on the “End Incident” button and confirm to end.

  3. Verify that the incident is ended.

Fix from 0.1.0

38

Non-commander cannot can end incident from post action menuwith /incident command.

  1. As user A, start an incident.

  2. As user B, verify that the incident is visible in RHS.

  3. Navigate to any channel.

  4. Post a message in the channel.

  5. Click on the post action menuIn the post input box, type `/incident'.

  6. Verify that there is no “Start Incident” /incidentoption present in the menuslash commands.

  7. As user A, add user B to the incident channel.

  8. As user B, navigate to the incident channel.

  9. Post a message in the incident channel.

  10. Click on the post action menuIn the post input box, type `/incident'.

  11. Verify that there is no “Start Incident” /incidentoption present in the menuslash commands.

38

Ending an incident shows a confirmation modal

  1. Start an incident.

  2. Open the In incident channel, issue /incident endcommand.

  3. When the end-incident-confirmation pops up, confirm to end.

  4. Verify that the incident is ended.

39

Incident cannot be ended from outside the incident channel

A post in incident channel appears when a new commander request is sent to a different user

Test procedure deleted

Test for v0.3.0

User receives a request when he/she is picked as a new commander for an incident

Test procedure deleted

Test for v0.3.0

User can deny the request to be a commander

Test procedure deleted

Test for v0.3.0

User can accept the request to be a commander

Test procedure deleted

Test for v0.3.0

A post in incident channel appears about the change in commander

Test procedure deleted

Test for v0.3.0

New commander can pick a different commander

Test procedure deleted

Test for v0.3.0

New commander can end incident

Test procedure deleted

Test for v0.3.0

Old commander cannot end incident

Test procedure deleted

Test for v0.3.0

Old commander can still access incident channel

Test procedure deleted

Test for v0.3.0.

Old commander is not kicked out of the incident channel upon picking a new commander

Old commander can still check off items in incident checklist

Test procedure deleted

Test for v0.3.0
Assuming that picking a new commander does not kick the older commander out of the incident channel

Old commander can still uncheck items in incident checklist

Test procedure deleted

Test for v0.3.0
  1. Create an incident.

  2. Ensure the user is navigated to the incident channel.

  3. Open RHS and find the incident just started.

  4. Click on it to view the details.

  5. Verify there is an the “End Incident” button at the bottom.

  6. Click on the button.

  7. Verify a confirmation modal pops up asking whether to end the incident.

  8. Go to the incident channel.

  9. In the post input box type /incident end

  10. Verify a confirmation modal pops up asking whether to end the incident.

39

Commander can end incident

Continue from the above test:

  1. Click to confirm ending the incident.

  2. Verify that the incident is ended.

(Incident end verifications in Test Plan - Incident Response v0.1.0 )

A non-commander cannot update the commander

Test procedure deleted

Test for v0.3.0

Old commander cannot end incident

Test procedure deleted

Test for v0.3.0

Commander can assign the commander role to different user

Test procedure deleted

Test for v0.3.0.
How does this appear on the new commander-to-be’s side? Do they need to approve/accept to be the new commander?

  1. exists in RHS.

  2. Navigate to a different channel than the incident channel.

  3. Verify that the “End Incident” changes to an inactive button, notifying the user that the incident can only be ended from within the incident channel.

Test Area - Measure

Test ID

Test Case

Test Procedure

Result

Notes

40

A bot message is posted in incident channel when an item is added to an incident checklist

  1. As a normal user, start an incident.

  2. The user is navigated to the incident channel.

  3. Open the Incident Response RHS.

  4. Find the incident started in step 1 and click to open details.

  5. Create a checklist and add an item.

  6. In the incident channel, verify that a bot message similar to the following is posted:

@username added checklist item "[checklist item title]"

41

“Item added to incident checklist” post in incident channel shows the username of user who added the item

Continue from the above test:

  1. Verify that the bot message from the above test shows the username of the user who added the checklist item.

42

Checklist item shows the timestamp of when the item was added

Continue from the above test:

  1. In the RHS, verify that the correct timestamp of when the item was added to the checklist is displayed beside the checklist item title.

https://mattermost.atlassian.net/browse/MM-23476 only talks about timestamp for checking off item

43

A bot message is posted in incident channel when an item in checklist is checked

  1. As a normal user, start an incident.

  2. The user is navigated to the incident channel.

  3. Open the Incident Response RHS.

  4. Find the incident started in step 1 and click to open details.

  5. Create a checklist and add an item.

  6. Check the item in step 5.

  7. In the incident channel, verify that a bot message similar to the following is posted:

@username checked off checklist item "[checklist item title]"

44

“Item checked” post in incident channel shows the username of user who checked the item

Continue from the above test:

  1. Verify that the bot message from the above test shows the username of the user who checked off the checklist item.

45

Checking an item shows the timestamp to the right of the checklist item of when the item was checked off

Continue from the above test:

  1. In the RHS, verify that the correct timestamp of when the item was checked off is displayed beside the checklist item title.

46

A bot message is posted in incident channel when an item in checklist is unchecked

  1. As a normal user, start an incident.

  2. The user is navigated to the incident channel.

  3. Open the Incident Response RHS.

  4. Find the incident started in step 1 and click to open details.

  5. Create a checklist and add an item.

  6. Check the item in step 5.

  7. Uncheck the item.

  8. In the incident channel, verify that a bot message similar to the following is posted:

@username unchecked item "[checklist item title]"

47

“Item checked” post in incident channel shows the username of user who unchecked the item

Continue from the above test:

  1. Verify that the bot message from the above test shows the username of the user who unchecked the checklist item.

48

Unchecking an item shows the timestamp to the right of the checklist item of when the item was unchecked

Continue from the above test:

  1. In the RHS, verify that the correct timestamp of when the item was unchecked is displayed beside the checklist item title.

https://mattermost.atlassian.net/browse/MM-23476 only talks about timestamp for checking off item

49

A bot message is posted in incident channel when an item is removed from an incident checklist

  1. As a normal user, start an incident.

  2. The user is navigated to the incident channel.

  3. Open the Incident Response RHS.

  4. Find the incident started in step 1 and click to open details.

  5. Create a checklist and add an item.

  6. Remove the checklist item.

  7. In the incident channel, verify that a bot message similar to the following is posted:

@username removed checklist item "[checklist item title]"

50

“Item removed from incident checklist” post in incident channel shows the username of who removed the item

Continue from the above test:

  1. Verify that the bot message from the above test shows the username of the user who removed the checklist item.

51

“Item removed from incident checklist” post in incident channel shows the timestamp of when the item was removed

Continue from the above test:

  1. Verify that the bot message from the above test shows the timestamp of when the item was removed from the checklist.

52

Starting a next incident will start with empty checklist

  1. Start an incident.

  2. Create a checklist for the incident.

  3. Check a few items and leave some unchecked.

  4. Start a new incident.

  5. View the incident details of the new incident.

  6. Verify that the incident does not have any checklist.

...