Test run object (or issue verification object generally)
A new object called a test run or a test execution or a feature verification.
The object would probably be created initially via the API in the beginning to support automated tests. But in the future it could be created manually via Web UI to support manual testing.
When an automated test is run by a pipeline, the pipeline script could call an API endpoint and pass this information to GitLab, creating the test run object.
- The pipeline itself. So pipeline ID.
- Zero, one, or multiple issue IDs. These issues represent feature(s), requirements, or test cases that the automated test is testing.
- Some test result. Pass, fail.
- A reason code or a free text field giving more context.
So GitLab will have a bunch of these test run objects in its database. It would serve these purposes:
- A feature to export the data to CSV that engineers could use to analyze the data.
- The test run objects would appear in some UI at the project and or group level so you can see it in a list view and sort and filter and order on.
- The test run objects would appear in associated issues. So if you look at a given issue page, you could see test runs that have been made against it, and click through to see the pipeline that created the test run.