diff options
Diffstat (limited to 'doc/ci/testing/unit_test_reports.md')
| -rw-r--r-- | doc/ci/testing/unit_test_reports.md | 22 |
1 files changed, 18 insertions, 4 deletions
diff --git a/doc/ci/testing/unit_test_reports.md b/doc/ci/testing/unit_test_reports.md index 8aa41cd6fc0..c8e0d6135df 100644 --- a/doc/ci/testing/unit_test_reports.md +++ b/doc/ci/testing/unit_test_reports.md @@ -145,8 +145,9 @@ GitLab does not parse very [large nodes](https://nokogiri.org/tutorials/parsing_ > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/202114) in GitLab 13.0 behind the `:junit_pipeline_screenshots_view` feature flag, disabled by default. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/216979) in GitLab 13.12. -Upload your screenshots as [artifacts](../yaml/artifacts_reports.md#artifactsreportsjunit) to GitLab. If JUnit -report format XML files contain an `attachment` tag, GitLab parses the attachment. Note that: +You can upload your screenshots as [artifacts](../yaml/artifacts_reports.md#artifactsreportsjunit) to GitLab. +If JUnit report format XML files contain an `attachment` tag, GitLab parses the attachment. +When uploading screenshot artifacts: - The `attachment` tag **must** contain the relative path to `$CI_PROJECT_DIR` of the screenshots you uploaded. For example: @@ -161,5 +162,18 @@ report format XML files contain an `attachment` tag, GitLab parses the attachmen [`artifacts:when: always`](../yaml/index.md#artifactswhen) so that it still uploads a screenshot when a test fails. -A link to the test case attachment appears in the test case details in -[the pipeline test report](#view-unit-test-reports-on-gitlab). +After the attachment is uploaded, [the pipeline test report](#view-unit-test-reports-on-gitlab) +contains a link to the screenshot, for example: + + + +## Troubleshooting + +### Test report appears empty + +A unit test report can appear to be empty when [viewed in a merge request](#view-unit-test-reports-on-gitlab) +if the artifact that contained the report [expires](../yaml/index.md#artifactsexpire_in). +If the artifact frequently expires too early, set a longer `expire_in` value for +the report artifact. + +Alternatively, you can run a new pipeline to generate a new report. |