Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,059
    • Issues 44,059
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,381
    • Merge requests 1,381
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #14394
Closed (promoted) (promoted)
Open
Created Apr 30, 2016 by Mike Wang@brisk

CI View for JUnit-style XML (origin issue)

Problem to solve

The user needs a way to more efficiently digest JUnit-style XML information so that they can find out why tests fail quicker.

Intended users

Further details

GitLab CI/CD shows job log information, so you can dig into why tests fail, but it requires humans reading a bunch of text. Most languages/frameworks are able to output JUnit XML (or xUnit, NUnit, PHPUnit, etc.)

Proposal

Implement a specific CI View (gitlab-ce#35379) for handling this kind of reports natively.

For this specific view, we should consider if we can force artifacts:when to always, so we can get failed tests results as well.

A test summary CI view which displays the following data for each failed test:

  • Test class
  • Test case name
  • Test status
  • Test run time
  • Stacktrace (containing failure type and failure message)
  • System Out
  • System error

Future Iterations

This JUnit XML epic &187 (closed) contains the priority of iterations for the CI view.

  • Display the first time this job failed https://gitlab.com/gitlab-org/gitlab-ce/issues/46613
  • We can determine which tests fail, not just which jobs (when a job runs many tests)
    • => We can display better summary information of failures
  • We can determine time taken for each test individually
    • => We can graph/analyze test durations over time
    • => We can use test duration to balance parallel jobs

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

Links / references

Original description:

Hi, just wondering if there is a way for me to view the junit report in a nicer way, similar to eclipse junit report?

This is my gitlab-ci.yml:

maven-build:
  script:
    - export DISPLAY=:99
    - /etc/init.d/xvfb start
    - mvn clean package
    - /etc/init.d/xvfb stop
    - rm /var/log/Xvfb/Xvfb_std.log
    - rm /var/log/Xvfb/Xvfb_error.log
    - rm -rf /var/log/selenium/Xvfb.pid

Currently, if a build failed, I have to click on the build and check the logs. I'd like to have a webpage displays the junit result similar to eclipse .

thanks

Edited Sep 11, 2019 by Dimitrie Hoekstra
Assignee
Assign to
Time tracking