The following 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.
| Stage | Plan |
| Maturity | Planned |
| Content Last Reviewed | 2021-08-09 |
Many organizations manage quality through both manual and automated testing. This testing is organized by test cases. These test cases can be run in different combinations and against different environments to create test sessions. Our goal for Quality management in GitLab is to allow users to track performance of test cases against their different environments over time, allowing for analysis of trends and identifying critical failures prior to releasing to production.
We have performed a Solution Validation for the Quality Management MVC.
The first step in building out Quality Management is a scaffolding framework for testing. In particular, we are calling these test cases, and test sessions. These will be first class native objects in GitLab, used to track the quality process of testing itself. The MVC can be seen at https://gitlab.com/groups/gitlab-org/-/epics/3852.
Over the next year, the Plan stage will be focused on consolidating Issues, Requirements and Epics into Work Items. Rationalizing the backend implementation will allow us to build Plan functionality more efficiently in the future. Due to that focus, we will not be dedicating significant capacity to the Quality Management category.
Competitors in this space include qTest, Test Rail, and HPQC (HP Quality Center). They are focused on managing test cases as part of the software development lifecycle. Our approach and response will be to have similar basic test case management features (i.e. test objects), and then quickly move horizontally to integrate with other places in GitLab, such as issues and epics and even requirements management. See https://gitlab.com/groups/gitlab-org/-/epics/670. With this strategy, we would not be necessarily competing directly with these existing incumbents, but helping users with the integration pains of multiple tools and leveraging other, more mature areas of GitLab as we iterate.
We have yet to engage more closely with analysts in this area. As this product category is prioritized for improvements as our Plan product and engineering headcount grows, we expect to engage more with analysts.
Few GitLab customers or prospects have asked about Quality Management. But the few that have, are asking about best practices and how they can possibly use GitLab and not worry with another tool. We are considering https://gitlab.com/groups/gitlab-org/-/epics/617 for that very purpose.
| Issue | 👍 |
|---|---|
| GitLab Quality Center | 36 |
| Test case management and test tracking in a Native Continuous Delivery way | 10 |
| Test cases and test suites | 8 |
We continue to work with GitLab's Quality Team to scope out the MVC of quality management. See https://gitlab.com/gitlab-org/gitlab/-/issues/216149.
The top Vision Item for this category is to release the MVC. It is our goal that by performing careful solution validation, we will come out with an initial offering for this product category which matches well with our target customers.
