Page Comparison

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

Invalid because only 10 of the most recent ongoing incidents are shown.

Test ID

Test Case

Test Steps

Result

Notes

E2E test done

42

Clicking on the incident icon when there are no incidents, opens the incident RHS to the “welcome” message

1. Install a fresh server.

2. As user-1, click the incident icon in the channel header.

3. Verify that the incident RHS opens with a “welcome” message to the user.

43

With incidents ongoing, clicking on the incident icon when user is in non-incident channel RHS opens up with the incident list for the user

Continue from the above test.

1. Create a playbook.

2. Start a new incident “I1”.

3. Navigate to a non-incident channel.

4. From the channel header, click the incident icon.

5. Verify that the incident RHS opens up with the list view showing the incidents user-1 is a member of.

44

With incidents ongoing, clicking on the incident icon when user is in incident channel with RHS open, shows the current incident details

Continue from the above test.

1. Go to the incident channel for “I1”.

2. Click the incident icon in the channel header.

3. Verify that the incident RHS opens with the incident list view, listing the incident created in the above test.

45

Switching from one incident channel to another incident channel with the RHS details view open will switch to the selected incident’s detail view in the RHS

Continue fromt he above test.

1. Create incident “I2”.

2. Click the incident icon in the channel header to open the details view for “I2” in incident RHS.

3. Navigate to incident channel for “I1”.

4. Verify that the details view in the incident RHS switches from “I2” to that of “I1”

46

The incident RHS list view has a “Start Incident” button in the RHS header

Continue from the above test.

1. Open the incident RHS list view.

2. Verify that the RHS header has a “Start Incident” button.

47

The “Start Incident” button in the RHS header opens up the incident creation modal

Continue from the above test.

1. Click the “Start Incident” button in the incident RHS header.

2. Verify that the incident creation modal opens.

48

The incident RHS list view has a “Create Playbook” button

Continue from the above test.

.

1. Go to an incident channel.

2. Open the incident RHS list view.

3. On the top right of the incident RHS, click the three dot menu.

4. Verify a “Create Playbook” button exists.

1. Click the button.

2. Verify that the playbook backstage opens.

49

A user can only see the incident he/she is a member of in the incident RHS list view

Continue from the above test.

1. Log in as user-3.

2. Click the incident icon in the channel header to open the incident RHS.

3. Verify that there are no ongoing incidents.

4. Create a new incident “I4” (create a playbook if necessary).

5. Click the incident icon in the channel header.

6. Verify that the incident RHS only lists “I4” in the list view.

7. Create a new incident “I5”.

8. Verify that the incident RHS lists “I4” and “I5” in the list view.

50

A user cannot see a public incident in the incident RHS if he/she is not a member of that incident

1. As user-1, create a public incident “PI1”.

2. Do not add any other user to the incident channel.

3. Log out and log in as user-2.

4. Open up the incident RHS list view.

5. Verify that incident “PI1” is not listed in the incident RHS for user-2.

51

“Click here to see all incidents” link in the bottom of the incident RHS list view takes the user to the incident backstage

1. As user-1, open up the incident RHS list view.

2. Verify that there is a “Click here to see all incidents” link in the RHS.

3. Click the link.

4. Verify that the incidents backstage page loads listing all the incidents that user-1 is a member of.

52

The incident RHS details view has a “back arrow” that brings a user to the incident list view in RHS

Continue from the above test.

1. As user-1, go to the incident channel for “PI1”.

2. If the incident details view is not already open in the incident RHS, open it up.

3. Verify that in the incident RHS header, there is a “<“ arrow.

4. Click the “<“ arrow.

5. Verify that the incident details view switches to the incidents list view.

53

Viewing the incident list from an incident channel highlights the current incident

Continue from the above test.

1. As user-1, start another incident “I-a1”.

2. Go to the incident channel for “I-a1”.

3. Open up the incident list view in the incident RHS.

4. Verify that in the list view, the entry for “I-a1” is highlighted.

5. Verify that none of the other incidents that user-1 is a member of is highlighted.

54

“Go to Incident Channel” takes the user to the associated incident channel

Continue from the above test.

1. From the incident list in the RHS, find the entry for “PI1”.

2. Click the “Go to incident Channel” button for “PI1”.

3. Verify that the incident channel for “PI1” is loaded.

4. Verify that the incident RHS changes to the incident details views for “PI1”.

55

“Go to Incident Channel” from a different team, takes the user to the correct incident channel in the right team.

Not sure about this behavior. Right now it shows a “Channel not found” error.

56

“Websocket updates should reflect changes automatically.” → what are the websocket updates?