Versions Compared

Version Old Version 3 New Version 4
Changes made by

Prapti Shrestha

Prapti Shrestha

Saved on

Key

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

Document version 0.0

Status: Test Completed

Document Version

Description

Date

0.0

Initial version

10/06

...

Is it an ephemeral message or a normal bot message that gets posted? Looks like a bot message

Test Area - User must be able to see the list of tasks in the current stage in mobile app

Test ID

Test Case

Test Steps

Result

Notes

E2E test done

14

/incident info is available as a slash command in mobile app

  • In mobile

    1. Type /incident in the main input box.

    2. In the slash command options pop up, verify that info is an available options.

  • In webapp

    1. Repeat mobile test steps above in webapp.

15

On mobile app, issuing /incident info command in incident channel posts an ephemeral message including the incident details

  1. As user-1, create a new playbook with only 1 Stage S1 and tasks T1 and T2.

  2. Start incident “M2”.

  3. Navigate to the “M2” incident channel.

  4. Issue an /incident info command.

  5. Verify that a system message displays the following accurately:

    1. Incident name: M2

    2. Duration of incident

    3. Commander of incident: user-1

    4. Stage: S1

    5. Tasks: T1, T2

16

On mobile, issuing /incident info command in non-incident channel posts a message that the info is only available in incident channels

  1. Go to a non-incident channel.

  2. Issue an /incident info command.

  3. Verify that a system message notifies the user that the details of an incident can only be viewed in an incident channel.

17

On webapp, issuing /incident info command in incident channel opens incident RHS if not already open

  1. Log in as user-1 in webapp.

  2. Go to the “M2” incident channel.

  3. Ensure that the incident RHS is not open (close if needed).

  4. Issue an /incident info command.

  5. Verify that the incident RHS opens showing the incident details.

Yes - E2E test PR

18

On webapp, issuing /incident info command in incident channel with a non-incident RHS open, opens incident RHS

Continue from the above test

  1. From the channel header, click the “Pinned posts” icon.

  2. Issue an /incident info command.

  3. Verify that the incident RHS opens showing the incident details.

  4. From the channel header, click the “Saved posts” icon.

  5. Issue an /incident info command.

  6. Verify that the incident RHS opens showing the incident details.

  7. From the channel header, click the “@ Recent mentions” icon.

  8. Issue an /incident info command.

  9. Verify that the incident RHS opens showing the incident details.

  10. From the channel header, search for a random term to trigger the search RHS.

  11. Issue an /incident info command.

  12. Verify that the incident RHS opens showing the incident details.

19

On webapp, issuing /incident info command in incident channel with incident RHS open posts a message that the incident details (or list?) is already open in incident RHS

Continue from the above test

  1. Ensure that the incident RHS is open.

  2. Issue an /incident info command.

  3. Verify that the incident bot notifies the user that the “incident details are already open in the RHS”.

20

On webapp, issuing /incident info command in non-incident channel posts a message that the info is only available in incident channels

Continue from the above test

  1. On webapp, navigate to a non-incident channel.

  2. Issue an /incident info command.

  3. Verify that the incident bot notifies the user that the incident details can only be viewed in an incident channel.

Yes - E2E test PR

Test Area - User must be able to see all their incidents in mobile app

Test ID

Test Case

Test Steps

Result

Notes

E2E test done

21

/incident list is available as a slash command in mobile app

  • In mobile

    1. Type /incident in the main input box.

    2. In the slash command options pop up, verify that list is an available options.

  • In webapp

    1. Repeat mobile test steps above in webapp.

22

Issuing an /incident list command when there is no incidents (fresh server) should show “There are no ongoing incidents in [team name] team” message for the user.

0. Install a fresh server.

  • In mobile

    1. Go to any channel and issue an /incident list command.

    2. Verify that the incident bot notifies the user that there are no ongoing incidents for the current team.

  • In webapp

    1. Repeat mobile test steps above in webapp

23

Issuing /incident list in non-incident channel shows all on going incidents

  1. Start a few incidents (< 10 incidents).

  2. In mobile, go to a non-incident channel.

  3. Issue an /incident list command.

  4. Verify that the incident bot posts a message with the incidents started in step 1 with the details including:

    1. link to the incident channel

    2. active stage

    3. duration

    4. commander of the incident

  5. In webapp, repeat steps 3-4.

24

Issuing /incident list in incident channel shows all on going incidents

Continue from the above test

  1. In mobile, go to an incident channel.

  2. Issue an /incident list command.

  3. Verify that the incident bot posts a message with the incidents started in step 1 with the details including:

    1. link to the incident channel

    2. active stage

    3. duration

    4. commander of the incident

  4. In webapp, repeat steps 2-3.

Issuing /incident list in incident channel shows all ongoin incidents if there are <= 10 ongoing incidents

Issuing /incident list show 10 of the most recent ongoing incidents if there are >10 ongoing incidents

25

Issuing /incident list does not show any incident that has been ended

Continue from the above test

  1. End an incident from the above test.

  2. In mobile, go to an incident channel.

  3. Issue an /incident list command.

  4. Verify that the incident bot does not list the incident that was ended in step 1.

  5. End another incident.

  6. Repeat steps 3-4

  7. In webapp issue an /incident list command.

  8. Verify that the incidents ended in steps 1 and 5 are not listed by the incident bot.

26

Issuing /incident list shows all incidents that have been restarted

Continue from the above test

  1. Restart the incidents ended in the above test.

  2. In mobile, issue an /incident list command.

  3. Verify that the incident bot lists all incidents.

  4. In webapp, issue an /incident list command.

  5. Verify that the incident bot lists all incidents.

27

Issuing /incident list does not show incidents from another team

  1. In mobile, as user-1 switch to a different team, Team Y; create one if needed.

  2. Issue an /incident list command.

  3. Verify that the incident bot notifies that there are no ongoing incidents in Team Y.

  4. In webapp, switch to Team Y.

  5. Repeat steps 2-3.

28

Issuing /incident list does not show incidents for another user

  1. Log in as user-2 (a user that has not started any incident).

  2. Issue an `/incident list` command in any channel.

  3. Verify that the incident bot notifies that there are no ongoing incidents in the current team.

29

/incident list should show all ongoing incidents for a large number of incidents

  1. Create a large number of incidents (>50).

  2. In mobile, issue an `/incident list` command.

  3. Verify that the incident bot lists all ongoing incidents.

  4. In webapp, repeat steps 2-3.

...