Skip to content

Rename JUnit reports to Unit Test Reports

Ricky Wiens requested to merge rw/unit-test-reports-no-junit into master

What does this MR do?

Having the name of the feature be "JUnit test reports" can cause confusion over what type of support this feature has. While it requires the JUnit report XML format, many different languages support that format. For a non-GitLab user/team member this could lead away from investigating a feature that might work well for them, just because their primary use case does not involve Java.



Related issues

Author's checklist (required)

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Marcel Amirault

Merge request reports