E2E test for Status Page with Incidents
Context
- The Status Page MVC epic
- Status Page Category Direction
Scope of the test
From the MVC criteria:
- All issues created within an incident project will be pushed to a new status site
- We will display a simple list of all of the incident issues. Since pagination will not be included in the MVC, we can limit this page to show last 20 incidents.
- For the first pass, there would be no sorting of active/closed incidents. But, we can address this piece in the future as part of a "full incident history" page.
- Clicking on the "full report" button on the incident landing page would open up the incident details on a separate page.
- The incident detail page will contain the issue description (including jpg/png images, if possible), the timeline, and issue comments. NOTE: not all issue comments will be published automatically to the status site. We'd like to utilize gitlab-org/gitlab#2459 (closed) when it is built. In the interim, we may need to utilize a stop-gap measure, such as we'll only push comments with a specific emoji attached to them.
Edited by 🤖 GitLab Bot 🤖