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

Maven Build - No Test found


Our java project uses maven to build and the project uses JUnit to let maven to run internal unit tests automatically. However, for every build process, the total test in each build is shown as zero. But in the log file, we see every build action triggers a set of unit tests and logs are shown to unit test results.

Would you advise where we need to configure such that Bamboo build can detect how many tests are included in a build process ?


1 answer

0 votes

Hi @Ray_Lee

Bamboo identifies the number/details of tests from test results. This is not an automatic task. Actually, you need to create a task to parse the results considering their file name, location, and format.

These are the parsing tasks you will find by default e.g. Bamboo 6.8.x:

The first one in the list is the one you need to configure to parse the test results your build is generating. Once that task is added and correctly configured you should be able to see the tests passing and failing for each build.

Please let me know if you face any issues with this.

Thanks Daniel.

May I know if JUnit test parser available for Bamboo version earlier than 4.x ? 


I was able to find reports for issues related to JUnit parsing for really old versions of Bamboo (before 4.x). While I cannot tell you precisely how the parser task was implemented in that time neither how the UI of it looked like (we are talking about a version of Bamboo released 7 years ago), I can tell that some resource was available.

I hope that is helpful.

thanks for your reply




Like Daniel Santos likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events