Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Document version 0.0

Status: Test development in progress

Document Version

Description

Date

0.0

Initial version

05/14

References

Related Tests:

Summary

This document details the tests for Incident Response plugin v0.5.0. The tests are derived from the user stories in Incident Response overview. The MVP of the Incident Response plugin will be tested against all tests included in this test plan.

Scope

This document covers the cases for the user stories as outlined in the Incident Response MVP Overview for v.0.5.0 of the plugin only.

Glossary

  • Admin - A user with system administrator privileges.

  • Normal user - A user with non-system administrator privileges.

  • Test Server - A list of test server versions used in testing including Mattermost server and Marketplace Server

  • Main menu - Hamburger menu on the LHS.

  • Incident Response icon - The Incident Response plugin icon that appears on the channel header

  • Commander - The user who owns an incident. The user who starts the incident is designated the commander by default.

  • Incident member/incident channel member - A user who has been added to the incident channel.

  • Non-incident user - A user who has not been added to the incident channel.

  • Active incident - An incident that has not been ended.

  • Ongoing incident - Same as Active Incident.

  • Inactive incident - An incident that has been ended.

  • Incident RHS - The RHS sidebar that opens upon clicking the incident response icon and displays incidents.

  • Incident Backstage - The backstage view that shows the incident list.

  • Playbook Backstage - The backstage view that shows the playbook list.

Assumptions

The tests in this test plans are written with the assumption that:

  1. The tests outlined in this document is to be executed against the Incident Response plugin v0.4.0.

  2. This version of the plugin can be installed and used in Mattermost instances that aren’t equipped with any enterprise license.

  3. The Incident Response plugin can function as a standalone plugin that does not require to talk to any other plugin.

  4. The Incident Response plugin will function in Mattermost version 5.12 and later

  5. The tests will be executed in Mattermost version 5.23.

  6. Testing is primarily done on the webapp, with spot checks on the desktop app, RN mobile app and mobile web browser app.

  7. The tests in this document are executed as a normal user (see glossary above) unless otherwise specified.

  8. The test cases that pass for a normal user will also pass for a system administrator.

  9. Plugin uploads is enabled in server instance

    1. “EnableUploads” option under “PluginSettings” in mattermost-server’s config.json is set to 'true'.

  10. The channel export feature defined in the user story is dependent on the existence of the Channel Export plugin being installed and enabled in the test server.

Setup

Document Setup

For the practicality of running tests easily, test cases are arranged in sequential order when necessary, following the preceding test case.

Test Setup

The following setup will be necessary in order to begin testing:

  • A Mattermost v5.23 test server.

  • The test server is equipped with an E10 license for the plugin to be installed.

  • Incident Plugin v0.5.0.

  • Channel Export Plugin v0.2

Test Server:

Test Server (upgrade tests):

Build Hash:

Test Date:

Tests

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.

 

 

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.3.

  2. Upgrade plugin to v0.4.

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

  4. Verify that incidents started with version 0.3 are still available in v0.4.

 

 

12

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

  1. Start a few incident with plugin version 0.3.

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

  3. Upgrade plugin to v0.4.

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

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

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

 

 

13

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

  1. Create a few playbooks with plugin version 0.3.

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

Test Area - Monitor

1: Give option for public vs private incident (and therefore channel) https://mattermost.atlassian.net/browse/MM-25178

Test ID

Test Case

Test Procedure

Result

Notes

2: Make it clear what is shown in RHS list

4: Incident duration in RHS https://mattermost.atlassian.net/browse/MM-25174

Test Area - Coordinate

3: Start incident in an existing channel https://mattermost.atlassian.net/browse/MM-24809

Test ID

Test Case

Test Procedure

Result

Notes

Test Area - Measure

Test ID

Test Case

Test Procedure

Result

Notes

Test Area - Tests/bugs outside of user stories

Test ID

Test Case

Test Procedure

Result

Notes

IR (v0.5.0) Bugs:

key summary type assignee reporter status resolution
Refresh

  • No labels