CharliePoole

Decide what to do about Incomplete specifications

1

The specifications section of the wiki contains a number of items that were never implemented or were only partially implemented. They need to be reviewed and incorporated in the docs...

General page on .NET Core only talks about the adapter

4

This page https://github.com/nunit/docs/wiki/.NET-Core-and-.NET-Standard is at the top level of the general NUnit menu, but it only gives info about using the VS adapter. Either it should be located under the...

Page at https://github.com/nunit/docs/wiki/XML-Formats needs significant updates. In particular, the section on progress events has almost no information.

Console option processing

1

@oznetmaster commented on [Thu Mar 19 2015](https://github.com/nunit/nunit/issues/549) In the help display for the console options, every option is prefaced by --. Also, the all show an = as the separator...

Run/Debug tests in context doesn't work correctly with generic fixtures

2

@martynsmall commented on [Tue Aug 12 2014](https://github.com/nunit/nunit-vs-adapter/issues/43) If you have a generic fixture and try running or debugging a single test by right clicking it in code and selecting 'Run...

Run NUnit V2 tests using the NUnit 3 adapter

1

This will require either separate installation of the V2 driver extension or bundling it with the NUnit 3 adapter. I'd prefer to keep them separate but its a little uncertain...

@CharliePoole commented on [Thu Oct 17 2013](https://github.com/nunit/nunit-vs-adapter/issues/11) We are having problem with the test adapter in our TFS build environment. Here are the versions used: - NUnit version 2.6.2 -...

@lawrencecraft commented on [Wed Mar 25 2015](https://github.com/nunit/nunit-vs-adapter/issues/67) Output from F#'s printfn is displayed with a newline after every character. See screenshots attached. Sample code: ``` module tests open NUnit.Framework []...