Unit testing ensures that individual components built within a pipeline perform as expected, and are an important part of a Continuous Integration framework.
Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.
This page is maintained by the Product Manager for Testing, James Heimbuck (E-mail)
We know that displaying the current code coverage value for a project is nice and displaying the value in a pipeline is valuable. We also know that without historical context it can be hard to understand what that value means today vs. yesterday. To solve this problem for users we are next going to add a graph for the code coverage value(s) displayed in the pipeline in (#33743).
This category is currently at the "Minimal" maturity level, and our next maturity target is "Viable" (see our definitions of maturity levels). Key deliverables to acheive this are:
The most popular issue in the Unit Testing category today is an interesting request to introduce a Checks API. This is a good first step towards cleaning up the appearance of the MR widget as more data is added there over time.
The QA department has opened an interesting issue gitlab#14954, aimed at solving a problem where they have have limited visibility into long test run times that can impact efficiency.
The top vision item is gitlab#3673 which will start to address the problem of flaky test results which cause developers to not trust test runs or force unnecessary reruns of tests. Both of those outcomes are undesirable and counter to our goal of minimizing the lead time of changes.