NUnit test results file compatibility with Bamboo NUnit Parser

We have a project that uses NUnit 2.5.9, for which the NUnit Parser tasks have been intermittently failing since we upgraded from Bamboo 4.1.2 to Bamboo 4.4.5; and I wondered if compatibility between Bamboo 4.4.5 and the NUnit 2.5.9 test result file may be an issue.

The Bamboo documentation does not specify which versions of NUnit are supported by the Bamboo NUnit Parser task. I have also noticed BAM-12433, which suggests that NUnit 3.0's file format is not yet supported.

Is the version or versions of NUnit supported by Bamboo 4.4.5 (or any other version) documented anywhere?

2 answers

1 accepted

0 votes
Accepted answer

I was able to work around the new behaviour in Bamboo 4.x that XML files created before the start of the current job are ignored by test result parsers by inserting a Script task prior to the test result parser task that executed the following two lines:

ping -n 3 > nul
forfiles /m *.xml /c "cmd /c copy /b @file +,,"

Hi Sean,

The supported versions are not documented any where unfortunately and I'll definitely collect more information and create a document for it.

From Bamboo 3.3 onwards, support for running NUnit is built in. Can you please navigate to Administration - > Manage Add-ons in Bamboo and check the version of the "Atlassian Bamboo .NET Plugin" under system Add-ons? Is it version 3.11? .

Did you have this add-on installed in your 4.1.2 from the marketplace: or you were using the built in?

If this continues to be a problem for you please file a support ticket with us, so we can do a more detailed search about this issue and be able to alook at your log files also.

Hope this helps!



Hi Sepideh,

I am using the built-in NUnit Result Parser in Bamboo 4.4.5. I am investigating the cause of a false build failure at this point and wondered if I need to be concerned about NUnit 2.5.9 result file format compatibility with Bamboo 4.4.5. The problem seemed to manifest after we upgraded to Bamboo 4.4.5 from Bamboo 4.1.2, but it may just be coincidence. The build fails complaining that the NUnit test results are either missing or invalid; we have confirmed in every instance that the files are present and valid (as far as we can tell). I will try upgrading NUnit to see if the situation improves, but a compatibility list would be helpful.

This continues to be a problem for us, so I've created a support ticket. It is unlikely that the problem is related to the parsing task itself, but perhaps to synchronization between stages and artifact sharing.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted 6 hours ago in Agile

What is Scrum? A good, bad, and ugly answer.

In a world of dark-scrum, faux-scrum, and scrum-butt, the question still remains: What is scrum and how do you do it “right?” That’s the question we set out to answer. I'm Max, I've been teaching c...

46 views 0 1
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you