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

Test results are only partially parsed into "Test"-view

I have a build task defined in Bamboo that runs unit- and integration-tests using maven surefire and maven failsafe respectively. 

Both plugins works perfectly fine and create the expected .xml report results for all tests that are being executed, regardless of them being unit- or integration-tests. 
Prior to a recent change all test results were generated by the surefire plugin, which after the build were correctly parsed into the build's "Test" view in for the Job.
The .xml output was created in **/target/surefire-reports/ (which seems to be the default folder for test results, yet those weren't correctly parsed if not specified directly in the job's settings, for some reason). Now the integration-test results are produced into a separate folder **/target/failsafe-reports/ which is also added to the jobs config to scan for test results. 

But since the change only the surefire-reports are being parsed and displayed as test-results. Even if only given the failsafe-reports folder in the job's config, those results are not parsed at all. The only difference in the generated xml-files is the schema location, which suggests that files not using the surefire-schema are being ignored categorically?

Does anyone have experience with a similar issue and knows a workaround to get Bamboo to parse these files as well? Currently there is no option to go back to the previous setup of the project only using one plugin, so this is what we're stuck with for the time being.

0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events