NUnit 3.0 is nearing its v3 release and bamboo has no support for running the tests. The xml output of nunit 3 has been change quite drastically to support many new features. The goal of this ticket is to add support for nunit 2.9.5+ in bamboo.
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BAM-12433] Support NUnit 3.0
Note that we support NUnit 3 by switching it to NUnit 2 compatibility mode. The actual NUnit 3 format is not supported, so if you're using tools other than NUnit to produce it, they won't work.
I just opened a support ticket for the same issue that @Robert Vandehey reports above. After upgrading from 5.13.0.1 to 5.14.3.1, all of our NUnit Runner tasks fail. We use NUnit 2.6.4.
What do you need to do to support nunit 3? Currently my builds are broken after upgrading with them failing due to nunit. I created a shim that simulated nunit 2.6 command line parameters and called nunit 3. That is now failing. So I tried switching to nunit 3.2.1 and I get a different failure. How does the task know whether to use the nunit 2.6 parameters or the nunit 3 parameters?
When Bamboo 5.14 version is going to be released? I hope it will really include the fix. It was very annoying finding the solution. Unfortunately I came to this page after found the fix.
Version 5.13.0.1 is affected too.
Glad to see that this will be fixed in the next version - we wanted to start using with bamboo because our old CI system does not support NUnit3 (amongst other issues) and I was a littble bit disappointed when I noticed that Bamboo does not support it too.
At the very least, the current plugin should note that it does not work under NUnit 3.0. I note that given the ease of fixing the problem for someone experienced in plugin coding (http://vijayshinva.github.io/devops/bamboo/nunit/tdd/ci/2016/02/25/configure-atlassian-bamboo-nunit-runner-to-execute-nunit-3-tests.html), it is disconcerting that the problem hasn't yet been addressed.
What does Status: Resolved, Resolution: Unresolved mean?
Will this not be fixed?
While waiting for this, I used the workaround from here: http://stackoverflow.com/a/35101907
Create a batch file and run that instead of nunit console directly - it replaces the "xml" arg with "result" and tells the result to be in nunit2 format:
@echo off SET "var=%*" CALL SET var=%%var:-xml=--result%% nunit3-console.exe %var%;format=nunit2
Andrew Newton
added a comment - - edited While waiting for this, I used the workaround from here: http://stackoverflow.com/a/35101907
Create a batch file and run that instead of nunit console directly - it replaces the "xml" arg with "result" and tells the result to be in nunit2 format:
@echo off
SET "var=%*"
CALL SET var=%%var:-xml=--result%%
nunit3-console.exe %var%;format=nunit2
Hi there,
I got the following error when using NUnit3 Runner in Bamboo v6.0.3.
I tried to add ";format=nunit2" in "Result Filename" and "Command Line Options", none of them works.