Skip to content
Snippets Groups Projects
Commit 4e12f87c authored by Marcel Amirault's avatar Marcel Amirault :interrobang:
Browse files

Merge branch 'rw/polish-unit-test-report-docs' into 'master' 

Unit test report docs polishing

See merge request !40765
parents 38258169 21befe4e
No related branches found
No related tags found
1 merge request!40765Unit test report docs polishing
Pipeline #183634474 passed with warnings
Stage: sync
Stage: prepare
Stage: build-images
Stage: fixtures
Stage: test
Stage: post-test
Stage: review-prepare
Stage: review
Stage: qa
Stage: pages
Stage: deploy
Hide whitespace changes
Inline Side-by-side
doc/ci/unit_test_reports.md
+ 3
− 5
View file @ 4e12f87c
......@@ -28,8 +28,6 @@ output without searching through job logs, the full
[Unit test reports](#viewing-unit-test-reports-on-gitlab) are available
in the pipeline detail view.
## Use cases
Consider the following workflow:
1. Your `master` branch is rock solid, your project is using GitLab CI/CD and
......@@ -44,9 +42,9 @@ Consider the following workflow:
## How it works
First, GitLab Runner uploads all JUnit report format XML files as artifacts to GitLab. Then,
when you visit a merge request, GitLab starts comparing the head and base branch's
JUnit report format XML files, where:
First, GitLab Runner uploads all [JUnit report format XML files](https://www.ibm.com/support/knowledgecenter/en/SSQ2R2_14.1.0/com.ibm.rsar.analysis.codereview.cobol.doc/topics/cac_useresults_junit.html)
as [artifacts](pipelines/job_artifacts.md#artifactsreportsjunit) to GitLab. Then, when you visit a merge request, GitLab starts
comparing the head and base branch's JUnit report format XML files, where:
- The base branch is the target branch (usually `master`).
- The head branch is the source branch (the latest pipeline in each merge request).
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment