Just thought I would share this in case anyone else runs into the same. We recently upgraded to NUnit3 for our web products, and the builds began failing. Turns out NUnit3 has new command line parameters and a new default XML output.
To work around this, I create a batch file shim called “nunit-console.bat” and placed it in the nunit3 console folder, with this content:
“C:\Program Files (x86)\NUnit.org\nunit-console\nunit3-console.exe” %1 --result=%3;format=nunit2
I then updated FinalBuilder to point to this batch file for launching nunit.
You also need to uncheck the “don’t display the logo” option in the nunit action.
-Britain
Just a note - this batch file works for a simple scenario where you are executing the tests within an assembly. If you are doing anything more complicated you will need to adjust the batch file.
Hi Britain,
We will be releasing full NUnit 3 support today. There is just some final testing that needs to be performed.
NUnit 3 is now supported in FinalBuilder 8. We will not be adding it to FB7.