Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E elsa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IP
  • elsa
  • Issues
  • #16

Closed
Open
Created Oct 21, 2019 by David Frank@david.frankMaintainer

Show JUnit reports in merge requests

GitLab provides the functionality to show failed tests in merge requests (see this). This nicely shows if any tests fail on a merge request, which don't fail on the master, or it just shows the failing tests, without having to go into the test logs or any such thing.

Suggestions

Catch provides additional arguments to catch_discover_tests, among those are reporters. We could have a global option, which would be activated while running CI builds, which automatically generate JUnit like reports and upload them as artifacts to GitLab-CI.

This is also a first try on how it looks, then we can decide if we want it

Assignee
Assign to
Time tracking