Test Plan - Incident Response v0.2.0
Document version 1.0
Status: Test for v0.2.0 completed
Document Version | Description | Date |
---|---|---|
0.0 | Initial version | 04/14 |
0.1 |
| 04/16 |
0.2 | Tests updated to reflect realtime checklist item editing. | 04/17 |
1.0 |
| 04/17 |
Summary
This document details the tests for Incident Response plugin v0.2.0. The tests are derived from the user stories in Release Detailsoverview.
The Test Areas in this document are arranged based on the vertical columns of the user storyboard.
The plugin will be available (see assumption) for Mattermost version starting 5.12 and up. This test plan consists of test cases to be run on Mattermost server version 5.22; however a subset of smoke tests will be executed on server versions 5.12, 5.14, 5.16, 5.18 and 5.20.
The tests in this document, together with the tests for other versions of the Incident Response plugin will be migrated to TM4J, upon the major plugin feature completion.
Scope
This test plan covers the tests for the user stories as outlined in the Incident Response MVP Overview for v0.2.0 and excludes tests for any other plugin version.
While some tests in this document also cover the bugs and stories resolved for the plugin v0.1.0, the tests for most bugs found during v0.1.0 testing are maintained in Test Plan - Incident Response v0.1.0.
Glossary remains the same as defined in Test Plan - Incident Response v0.1.0
Assumptions
The tests outlined in this document is to be executed against the Incident Response plugin v0.2.0.
This version of the plugin can be installed and used in Mattermost instances that aren’t equipped with any enterprise license.
The Incident Response plugin can function as a standalone plugin that does not require to talk to any other plugin.
The Incident Response plugin will function in Mattermost version 5.12 and later
The tests will be executed in Mattermost version 5.22.
Testing is primarily done on the webapp, with spot checks on the desktop app, RN mobile app and mobile web browser app.
The tests in this document are executed as a normal user (see glossary above) unless otherwise specified.
The test cases that pass for a normal user will also pass for a system administrator.
Plugin uploads is enabled in server instance
“EnableUploads” option under “PluginSettings” in mattermost-server’s config.json is set to 'true'.
Setup
Document Setup
For the practicality of running tests easily, test cases are arranged in sequential order when necessary, following the preceding test case.
Some details in the test procedures have been omitted to reduce the redundancy in test steps if they are clear enough and extensively covered in the test plan for v0.1.0.
Test Setup
The following setup will be necessary in order to begin testing:
A Mattermost v5.22 test server.
The test server is equipped with an E10 license for the plugin to be installed.
Incident Plugin v0.2.0.
Tests
Test Server: https://wf-test-te.test.mattermost.cloud/
Server Version: release-5.22
Build Hash: 64922547a34fed47c045cc14273a8f86f0c1b9fa
Test Date: 04/17/2020
Test Area - Plugin Setup | ||||
---|---|---|---|---|
Test ID | Test Case | Test Procedure | Result | Notes |
1 | Admin can install plugin in a non-EE instance |
| Pass | Plugin is Enabled by default |
2 | Admin can install plugin in an E10 instance |
| Pass |
|
3 | Admin can install plugin in an E20 instance |
| Pass |
|
4 | Admin can enable plugin |
| Pass |
|
5 | Plugin functionality is available to admin |
| Pass |
|
6 | Plugin functionality is available to normal user |
| Pass |
|
7 | Admin can disable plugin |
| Pass | UI funkyness - MM-24338: Post action menu shows a blank section at the end after corresponding plugin is disabledClosed |
8 | Admin can remove plugin |
| Pass |
|
For the next set of tests, begin with the following steps:
Login as an admin user
Enable the Incident Response plugin
Navigate to System Console > PLUGINS > Plugin Management.
In “Installed Plugins” find Incident Response and click “Enabled”.
Log out.
Test Area - Monitor | ||||
---|---|---|---|---|
Test ID | Test Case | Test Procedure | Result | Notes |
9 | User is taken to incident channel after starting an incident |
| Pass | Did not always get navigated to incident channel when starting from post action menu |
10 | In RN mobile app, user is notified with an ephemeral message with link to the incident channel |
| Pass |
|
11 | A newly started incident does not have any checklist item |
| Pass |
|
12 | Commander can create a checklist for an incident started by them |
| Pass |
|
13 | Commander cannot create a checklist for an incident from a channel different from the incident channel |
| Pass |
|
14 | Checklist “edit” button does not work when checklist is empty |
| Pass |
|
15 | Checklist item creation can be cancelled with the Esc key |
| Pass |
|
16 | Commander can create checklist item from within the channel incident view |
| Pass |
|
17 | Checklist item can be added in edit view. |
| Pass |
|
18 | Commander can remove checklist item from an incident started by them |
| Pass |
|
19 | User only has read-only access to an incident checklist if user is not an incident channel member |
| Pass |
|
20 | User cannot add checklist item to a new incident started by a different user if user is not added to the incident channel |
| Pass |
|
21 | User cannot add items to a checklist, with existing items, for an incident started by a different user if user is not added to the incident channel |
| Pass |
|
22 | User cannot remove checklist item from an incident started by a different user if user is not added to the incident channel |
| Pass |
|
23 | Incident checklist is no longer read-only once non-commander is added to incident channel |
| Pass |
|
24 | User can add checklist item to a new incident started by a different user once added to the incident channel |
| Pass |
|
25 | User can add items to a checklist, with existing items, for an incident started by a different user once added to the incident channel |
| Pass |
|
26 | User can edit the checklist item for an incident started by a different user once added to the incident channel |
| Pass |
|
27 | User can move items around in the checklist once added to the incident channel |
| Pass |
|
28 | User can remove item added by different user once added to the incident channel. |
| Pass |
|
29 | Checklist item added reflects accurately for user not added to incident channel |
| Pass |
|
30 | Checklist item edited reflects accurately for user not added to incident channel | Continue from the above test.
| Pass |
|
31 | Checklist item rearranged reflects accurately for user not added to incident channel | Continue from the above test.
| Pass |
|
32 | Checklist item removed reflects accurately for user not added to incident channel | Continue from the above test.
| Pass |
|
33 | Checklist changes reflect accurately for a different user added to incident channel |
| Pass |
|
34 | Checklist can be added by 2 users at the same time when they are both incident channel members |
| Pass |
|
35 | Checklist can be edited by 2 users at the same time when they are both incident channel members | Continue from the above test.
| Pass |
|
Test Area - Coordinate | ||||
---|---|---|---|---|
Test ID | Test Case | Test Procedure | Result | Notes |
36 | Commander can check off items in incident checklist |
| Pass |
|
37 | Commander can uncheck items in incident checklist |
| Pass |
|
38 | Non-commander who is not added to incident channel cannot check off items in incident checklist |
| Pass |
|
39 | Non-commander who is not added to incident channel cannot uncheck items in incident checklist |
| Pass |
|
40 | Non-commander user, who is added to the incident channel, can check off items in incident checklist |
| Pass |
|
41 | Non-commander user, who is added to the incident channel, can uncheck items |
| Pass |
|
42 | Non-commander user, who is added to the incident channel, can uncheck items checked off by the commander |
| Pass |
|
43 | Ending an incident shows a confirmation modal |
| Pass |
|
44 | End incident confirmation modal can be dismissed by clicking Cancel |
| Pass |
|
45 | End incident confirmation modal can dismissed by pressing Esc |
| Pass |
|
46 | Commander can end incident | Continue from the above test:
(Incident end verifications in Test Plan - Incident Response v0.1.0 ) | Pass |
|
47 | Non-commander cannot can end incident from RHS |
| Pass |
|
48 | Non-commander cannot can end incident with |
| Pass |
|
49 | Incident cannot be ended from outside the incident channel |
| Pass |
|
Test Area - Measure | ||||
---|---|---|---|---|
Test ID | Test Case | Test Procedure | Result | Notes |
50 | A bot message is posted in incident channel when an item is added to an incident checklist |
| Pass |
|
51 | “Item added to incident checklist” post in incident channel shows the username of user who added the item | Continue from the above test:
| Pass |
|
52 | A bot message is posted in incident channel when an item in checklist is checked |
| Pass |
|
53 | “Item checked” post in incident channel shows the username of user who checked the item | Continue from the above test:
| Pass |
|
54 | 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:
| Fail | For v0.3.0 |
55 | A bot message is posted in incident channel when an item in checklist is unchecked |
| Pass |
|
56 | “Item checked” post in incident channel shows the username of user who unchecked the item | Continue from the above test:
| Pass |
|
57 | A bot message is posted in incident channel when an item is removed from an incident checklist |
| Pass |
|
58 | “Item removed from incident checklist” post in incident channel shows the username of who removed the item | Continue from the above test:
| Pass |
|
59 | “Item removed from incident checklist” post in incident channel shows the timestamp of when the item was removed | Continue from the above test:
| Pass |
|
60 | Starting a next incident will start with empty checklist |
| Pass |
|
Test Area - Extra bugs found during release testing | ||
---|---|---|
Test Case/Bug Title | Test Procedure | Note |
Channel links refresh current channel if incident channel is archived before ending incident when "view archived channels" is false |
Observed: The current channel page refreshes. Expected: User is notified that the "view archived channels" should be enabled to navigate to the channel. | |
"Internal error" message when starting an incident from system message post action menu |
|
Smoke tests for server versions 5.12, 5.14, 5.16, 5.18 and 5.20
Subset of tests to run on different server versions, mobile app and mobile browser
Installation
Enabling the plugin
Disabling the plugin
Starting an incident
Viewing an incident
Ending an incident