Define Test Cases from within GitLab
This issue represents the first step toward implementing the MVC for Quality Management.
Problem Statement
Build on top of the extensible issue work being performed and create a new issuable type for test cases. To start, this test case issuable would need the following additional widgets
built on top of the default base type (see technical example):
Primary Container
- description
Primary Tabbed
- none
Secondary Container (right sidebar)
- labels
Over time, we will be able to add additional custom widgets for test cases such as:
- Environment
- Pass / Fail status (per environment)
- discussions
In order to commence testing, test case issues can be duplicated as test runs. This will allow them to be linked to the parent tase case, and allow pass / fail information to be passed back to the parent test case for display.
GitLab Tier
Referencing the guidance on the Buyer Based Tiering Clarification, it would appear that the Quality Management would fall into the GitLab Ultimate tier.
Tasks
See discussion
1. Allow to create/view test cases:
- Backend - Add test cases controller/routes, feature flag and license check 2 !40019 (merged)
- Backend- Allow to create issues with test case type only on ultimate tier 2 !40306 (merged)
- Backend - Add GraphQL mutation to create test cases 1 !41190 (merged)
- Backend - Allow to filter issues/test_cases by author 1
- Frontend - Create test cases 2 !41559 (merged)
- Frontend - Display test cases list 2 !41998 (merged)
- Frontend - Show a Test Case 3
2. Allow to update test cases
- Frontend - Add form to update test cases(use UpdateIssue mutation) 2
- Backend - Allow issue mutation to update state 2 !44061 (merged)
- Backend - Allow to move issues on Graphql 2 !44491 (merged)
3. Add test cases label support
- Frontend work 2
4. Edge cases
- Backend - Hide test cases from projects issues list 1 !42092 (merged)
- Backend - Hide test cases from group issues list 1 !44052 (merged)
- Backend - Hide test cases from issue boards 1 !44196 (merged)
- Backend - Allow to create Todo for test cases 2 !46029 (merged)
- Backend - Expose UpdatedBy field on GraphQL for test cases 1 !46015 (merged)
Acceptance Criteria
The minimum required functionality for this iteration is for the user to be able to perform the following:
- Navigate to a list of test cases
- View the current list of created test cases
- Click on an existing test case and view / edit the enabled fields (see above)
- Have a means of creating a new test case
- Archive a test case (essentially the same as how we
close
an issue)
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.