Document version 0.0
Status: Test development in progress
...
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 As a user of a team, I can see a list of all past and current incidents within the team so that the information is not lost. | ||||
|---|---|---|---|---|
Test ID | Test Case | Test Procedure | Result | Notes |
Clicking | ||||
Backstage shows a tab for incidents | ||||
Clicking on “Incidents” tab on backstage LHS highlights the Incidents tab | ||||
Clicking on “Incidents” tab on backstage LHS loads the list of all incidents | ||||
The incidents list view displays the team name the incidents belong to | ||||
The incident list in the backstage displays the following columns: name, status, start timestamp, end timestamp and the commander | ||||
The incident list in the backstage shows all active incidents that belong to the current team only | ||||
The incident list in the backstage shows all inactive incidents that belong to the current team only | ||||
Active incidents show an “Ongoing” status in the | ||||
Inactive incidents (ended incidents) show an “Ended” status in the | ||||
The incident list in the backstage shows updated end timestamp for an incident | ||||
An active incident shows “Ongoing” in End Date column | ||||
The incident list in the backstage shows updated commander for an incident | ||||
The incident names in the “Name” column render as clickable links | ||||
Long incident name wraps in the “Name” column displaying the entire incident name | ||||
As the incident plugin, the channel is automatically archived when the incident ends so that it reduces clutter. | ||||
Channel is archived when ending an incident with slash command | ||||
Channel is archived when ending an incident from RHS | ||||
The incident channel is no longer available on the LHS once the incident is ended | ||||
The incident channel shows up under archived channel once the incident is ended | ||||
Test Area - Coordinate As a user, I can export channel transcript from the incident detail page so that it can be saved for record | ||||
|---|---|---|---|---|
Test ID | Test Case | Test Procedure | Result | Notes |
When Channel Export plugin is not installed, the “Export Incident Channel” link is inactive and appears in greyscale | To admin To incident member To non-member | |||
When Channel Export plugin is not installed, hovering over the “Export Incident Channel” link shows a message to “install the channel export plugin” | To admin To incident member To non-member | Install the channel export plugin to support exporting this incident. | ||
When Channel Export plugin is installed in an instance with no EE license, the “Export Incident Channel” link is inactive and appears in greyscale | To admin To incident member To non-member | |||
When Channel Export plugin is installed in an instance with no EE license, hovering on the “Export Incident Channel” link shows a message that “E20 license is required” | To admin To incident member To non-member | Exporting an incident channel requires a Mattermost Enterprise E20 license. | ||
When Channel Export plugin is installed in an instance with an E10 license, the “Export Incident” link is inactive and appears in greyscale | To admin To incident member To non-member | |||
When Channel Export plugin is installed in an instance with an E10 license, hovering on the “Export Incident Channel” link shows a message that “E20 license is required” | To admin To incident member To non-member | Exporting an incident channel requires a Mattermost Enterprise E20 license. | ||
When Channel export plugin is installed but not enabled, the “Export Incident Channel” link is inactive and appears in greyscale | To admin To incident member To non-member | |||
When Channel Export plugin is installed but not enabled, hovering over the “Export Incident Channel” shows “enable the plugin” message | To admin To incident member To non-member | Enable the channel export plugin to support exporting this incident. | ||
When Channel Export plugin is installed and enabled, an active “Export Incident Channel” link and icon is available in the backstage incident list view | ||||
When Channel Export plugin is installed and enabled, hovering over the “Export Incident Channel” link shows a message that the action will download the channel content | ||||
An incident member can export the incident channel by clicking “Export Incident Channel” link | Link is not in greyscale Shows action when clicked | |||
Clicking the “Export Incident Channel” link downloads the csv file of the incident channel | ||||
The exported csv file captures the current status of the incident | ||||
Admin can export the incident without being a member of the incident channel | ||||
“Export Incident Channel” button shows as a grey-inactive button to non-incident user | Should not be able to click | |||
A non-incident user sees a “no access” message upon hovering on the “Export Incident Channel” button | You do not have access to this incident channel. Contact the commander to export this incident. | |||
Verify the appearance of the “Export Incident Channel” link and icon appear in dark theme | ||||
Verify the appearance of the “Export Incident Channel” link and icon appear in other themes | ||||
Exporting an ended incident channel from backstage | ||||
As the incident commander, I receive an incident summary and a link to more info after ending an incident so that I know where to go for post-mortem. | ||||
Test Area - Measure As a user, I can see a summary of the following on incident detail page so that I can get the gist at a glance:
| ||||
|---|---|---|---|---|
Test ID | Test Case | Test Procedure | Result | Notes |
User cannot view incident summary if the user is not an incident member | ||||
From the incidents list in the backstage, user can navigate to incident summary upon clicking the incident name of an active incident if the user is an incident member | ||||
From the incidents list in the backstage, user can navigate to incident summary upon clicking the incident name of an inactive incident | ||||
Incident summary page displays the incident name as the page heading | ||||
Incident summary page has a “<“ button that brings a user back to the incidents list view | ||||
Incident summary page bears a link to the incident channel | ||||
Hovering on the incident channel link shows a tooltip suggesting that it’s a shortcut to the incident channel | ||||
Clicking on incident channel link of active incidents brings the user to the incident channel | ||||
Clicking on incident channel link of inactive incidents, when | ||||
Clicking on incident channel link of inactive incidents, when | ??? | |||
Incident summary shows the current status of the incident | ||||
Incident summary shows the current commander of the incident | ||||
For active incidents, incident summary shows the duration of how long the incident has been active for | ||||
For inactive incidents, incident summary shows the duration of how long the incident remained active for before the incident ended | ||||
For active incidents, incident summary shows the current number of members in the incident channel | ||||
For an inactive incident, incident summary shows the number of member in the incident channel when the incident was ended | ||||
For active incident, incident summary shows the total number of messages in the incident channel | ||||
For inactive incident, incident summary shows the total number of messages in the archived channel of the inactive incident | ||||
...