CharliePoole

@akazakov8591 If you are running with ReSharper then you are not running with the NUnit 3 VS Adapter and our fix won't help you. :-( Since ReSharper is proprietary, I...

@patrickjamesbarry Not the same issue. Explicit is a test state that is known by NUnit but unknown to Visual Studio so it requires special handling. Ignore should be well understood...

Are you getting the list of tests to run from VS? Once you have a list of tests from VS, you are going to run explicit tests. There is no...

@rprouse As you know, the adapter is called directly from VS and has a separate entry point used when the user selects "run all" or when vstest console is used....

@filmor Not sure I understand.... Let's say that VS tells us to run a mix of tests, some Explicit, some not. We don't have that info readily available, but it...

Additionally, it might be worthwhile to wait and see how much we are able to bring together the engine code and this project's. We already have two implementations of the...

As a workaround, you could leverage the code for NUnit's V2 result writer, which takes an XmlNode in V3 format and creates an output file in V2 format. https://github.com/nunit/nunit-console/tree/master/src/NUnitEngine/Addins/nunit-v2-result-writer

Writing a transform to go from NUnit 3 to NUnit 2 format would seem like a waste of time, given that we already have C# code that does the same...

@nepdev Thanks for checking! @rprouse Looks like this is particular to dotnet-test-nunit then.

Huh! I wasn't aware it was supposed to work with classic .NET assemblies.