Test Plan for 'Promote issue to epic with quick action'
Test Plan
Introduction
This is the test plan for https://gitlab.com/gitlab-org/gitlab-ee/issues/3777
Scope
- This is the plan to test quick actions for promoting an issue to an epic.
- This test focuses on functional testing of:
- UI Level E2E Tests - Needs to be automated
- Out of scope: System notes specific to closing the issue and creating the epic are out of scope.
- Out of scope: Labels handled in a separate issue
ACC Matrix
Based on Google Testing Blog article about the 10 minute test plan and ACC Explained
| Simple | Secure | Responsive | Obvious | Stable | |
|---|---|---|---|---|---|
| /promote | 2 | 2 | 1 | 1 | 1 |
Capabilities
- /promote is
- Simple
- Promoting an issue (closed or open), creates a new epic and closes the original issue.
- Promoting an issue which is already a part of an epic, creates a new epic and closes the original issue. (original epic - issue relationship remain as such)
- Secure
- Confidential Issues should not be promoted to epic.
- Issues from a private project should not be promoted to epic
- Responsive
- Promoting issues, triggers email notification to all participants.
- Obvious
- Title, description and activity/comment thread remains in tact.
- Stable
- With nested subgroups, promoting an issue in a subgroup's project, creates an epic in the immediate parent only.