Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NUnit 3 console support #1010

Closed
dlsteuer opened this issue Nov 17, 2015 · 7 comments
Closed

NUnit 3 console support #1010

dlsteuer opened this issue Nov 17, 2015 · 7 comments

Comments

@dlsteuer
Copy link

NUnit 3 has just been released and the options to the console runner (now called nunit3-console.exe) have been changed.

Some examples of changed options are:

  • -nologo has changed to -noheader
  • -noshadow has changed to -shadowcopy and the semantics of it are inverted
  • -labels has changed to require a value -labels=VALUE (Off, On, All)

Also it appears the output xml format has changed, but can be forced into nunit2 format with an option.

@7sharp9
Copy link
Member

7sharp9 commented Nov 20, 2015

This breaks existing build scripts as nunit-console.exe no longer exists, so when NUnit tasks are executed you get a file not found :-(

@forki
Copy link
Member

forki commented Nov 20, 2015

yes you need to do "nuget NUnit ~> 2" in your dependencies file.
The FAKE support is only for NUnit 2.x - until someone writes a new helper or somehow detects the version and does some magic.

@7sharp9
Copy link
Member

7sharp9 commented Nov 20, 2015

Yeah a lot of scripts just take the latest, like projectscaffold etc

@forki
Copy link
Member

forki commented Nov 20, 2015

yeah bad timing ;-)

@neoeinstein
Copy link
Contributor

This seams like a prime opportunity for me to give the NUnit runner the same treatment I gave XUnit. I'll take a swing through this over the weekend.

@fstaffa
Copy link
Contributor

fstaffa commented Jan 5, 2016

Created NUnit 3 support, PR is here: #1064

@aprooks
Copy link

aprooks commented Jun 14, 2016

@forki should this issue be closed due to #1064 merge?

@forki forki closed this as completed Jun 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants