NUnit wish to drop supporting NUnit v2 in the upcoming NUnit v4 release:

https://github.com/nunit/nunit-v2-result-writer/issues/13

https://github.com/nunit/nunit-console/issues/879

@Nikita

Yeah that has been our experience as well. FWIW I cannot recall how much Unity wrapped the NUnit Runner, but you can pass a Result Spec to the NUnit Console Runner (https://docs.nunit.org/articles/nunit/running-tests/Console-Command-Line.html#description) in this manner:

nunit3-console.exe UnitTest.dll --result=TestResult.xml;format=nunit2

This should save you having to run any additional post execution conversion tool like the above linked one. It does require that you have that plugin selected to install if you are using the NUnit3-Console MSI that ships from NUnit.org.

@Ace doesn't seem to be the case.

I'm using unit tests runner in Unity project which outputs nunit3 results. I had to run converter on the produced reports to be able to view them properly in bamboo ( https://github.com/wooga/NUnit3-to-NUnit2-Format-Converter )

Hi we're currently evaluating Bamboo/BitBucket/Jira for a large rollout internally.

Does BambooCI Still not support The NUnit3 Result Format?

Quick workaround to use nunit3 format:

1) Set executable to .bat script

2) Create bat:

// @echo off
set parameters=%1 %2=%3;%4=nunit3
SHIFT
SHIFT
SHIFT
SHIFT
SHIFT
:loop
SHIFT
if [%0]==[] GOTO afterloop
SET parameters=%parameters% %0
GOTO loop
:afterloop
echo %parameters%
C:\tools\NUnit.ConsoleRunner.3.10.0\tools\nunit3-console.exe %parameters%

I figured out a solution to my problem. Instead of using NUnit XML format, I use TRX format (see argument below), and then I add the MSTest Parser task in Bamboo. After that, the passed tests correctly show as passed

--logger trx;LogFileName=results.trx

@Mike Johnston Same here. But i hope the feature will be implemented soon.

@Stefan Bucherl Yes I also wondered about my build failing when at least 1 test fails. However, is that the intended functionality of Bamboo builds? Because I do not see a 'Passed Test' section, do you see it?

@Mike Johnston No we are still at 6.8 and still skipped tests. But the build fails if at least one test fail. Thats not good but works temporarely

@Stefan Bucherl I am not sure, I will check with my DevOps. Are you on 6.9 or later? Are the Passed tests still showing as Skipped? If not, what fixed it?