Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How test reporting on Bitbucket Pipelines works?


Hi community,

I'm struggling to make test reporting work on Bitbucket Pipelines.
- My maven project defines a couple of JUnit tests.
- Test reports are generated by maven surefire plugin on the right place at first glance.


This is an excerpt of my pipelines log:

+ pwd

+ ls -lia target/surefire-reports/*.xml
5522980 -rw-rw-rw-. 1 root root 62399 Jul 15 15:54 target/surefire-reports/

Which looks like good, as xml reports are located in one of the default scanned paths following the documentation:

Configuring test reporting

To enable test reporting, make sure that build test reports are generated in one of the supported default locations (with a directory depth of 3 levels):






The test report file scanner will begin searching from the base directory of your build: /opt/atlassian/pipelines/agent/build

Configuring test runners

Maven Surefire / Failsafe plugins

For Maven build jobs, no special configuration is required if you are using Maven Surefire Plugin or Maven Failsafe Plugin. The reports are automatically generated when the unit or integration maven test goals are executed.

4 answers

1 accepted

1 vote
Answer accepted

Hello @Jack Nolddor _Sweet Bananas_

Thank you for the detailed description. It was very helpful!

Once I read It I went right away to test it myself and observe the same behavior. Which is:

If the test passes 
    You will only see them reported in the left panel beside the pipeline step name.

If the test fails
    You will see a new tab with the reports for the tests that failed.

My first glance was to check our docs to see if this information was available there and it was:

Note: the Tests tab will only show if you have failed tests to review.

I guess I learned something today =]

Please confirm if this is the same scenario you see there otherwise we will need to investigate this a bit further.

Quite interesting and confusing behaviour hehehe
I expected to see Test tab whenever my build finished either fail or success.

Thanks for resolve this mistery.

Like # people like this

I guess it was intended by design assuming that passed tests will not be reviewed.
I'm glad to be helpful!

It still can be useful to review the test results to analyze which tests take most of the suite time.

Hey guys,
here is the ticket Bitbucket team created for this issue:

The current issue status is "Gathering Interest", so please go and vote for it if you are still interested.


Thanks for sharing

I was scratching my head for a while as well - but same experience here. Successful tests do not show a tab, while failures do. Kinda stupid...but at least we know now :)

Thanks for the post. I got caught by this... for the 2nd time over the years perhaps. Upvoted the open issue.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events