Does not work after migrating to csproj

[trampster]

This message is displayed:

No test discoverer is registered to perform discovery of test cases. Register a test discoverer and try again.

This is my csproj file:

 <PropertyGroup>
     <OutputType>Exe</OutputType>
     <TargetFramework>netcoreapp1.1</TargetFramework>
 </PropertyGroup>

 <ItemGroup>
     <ProjectReference Include="../Jsonics/Jsonics.csproj" />
 </ItemGroup>

 <ItemGroup>
     <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0" />
     <PackageReference Include="NUnit" Version="3.6.0" />
     <PackageReference Include="dotnet-test-nunit" Version="3.4.0-beta-3" />
 </ItemGroup>

[rprouse]

The new CSPROJ format officially deprecates support for the dotnet-test-* test adapters for running unit tests. Tests will be run in VS and on the command line using the old Visual Studio adapters. We haven’t converted our VS adapter to support .NET Core yet though, so the only way to run NUnit tests will be to make them self-executing using NUnitLite.

@rprouse Can you please give an example of how I can run my Nunit tests using NUnitLite on netcoreapp1.1?

[rprouse]

@sepidehkh I hope to write an updated blog post about how to do it soon, but in the meantime, my original .NET Core blog post should get you started. http://www.alteridem.net/2015/11/04/testing-net-core-using-nunit-3/

To make the migration easy, you can leave your tests as-is and add a .NET Core console app to be the runner. Reference your tests and use one of your tests classes as the constructor to AutoRun.

Let me know how it goes...

Thank you @rprouse! That fixed my problem.

[mayuanyang]

how about xunit?
<ItemGroup> <PackageReference Include="dotnet-test-xunit" Version="2.2.0-preview2-build1029" /> <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0" /> <PackageReference Include="Shouldly" Version="2.8.2" /> <PackageReference Include="System.Console" Version="4.3.0" /> <PackageReference Include="TestStack.BDDfy" Version="4.3.2" /> <PackageReference Include="xunit" Version="2.2.0" /> </ItemGroup>

[rprouse]

@mayuanyang xunit works, but that isn't useful for people who prefer NUnit or have many unit tests to convert. We know that NUnitLite is not a viable solution in the long-run, but it will hopefully hold people over in the short term while we update the adapter.

[toralux]

Reference your tests and use one of your tests classes as the constructor to AutoRun.

What do you exactly mean by "use one of your tests classes as constructor to AutoRun?

Basically I use AutoRun like this, but still no tests are discovered or run:
return new AutoRun(typeof(Program).GetTypeInfo().Assembly).Execute(args, new ExtendedTextWrapper(Console.Out), Console.In);

All tests are in same assembly/project as the console-app starting AutoRun

Update: Got this in my Output-window:

An exception occurred while test discoverer 'NUnit3TestDiscoverer' was loading tests. Exception: Method not found: 'System.Xml.XmlNode NUnit.Engine.ITestRunner.Explore(NUnit.Engine.TestFilter)'.
========== Discover test finished: 0 found (0:00:00,7601484) ==========```

[csbondeson]

@rprouse I am trying to use your suggested NUnitLite setup but I need to be able to output the results preferably in the nunit2 format, is this possible? The command that I have been using in the nunit3-console.exe is "{ProjectDll} --result nunit-tests.xml;format=nunit2". Any help would be greatly appreciated.

[csbondeson]

I tried just sending those exact same args into my command line and it seemed to work so you can ignore my previous question.

I would like to know if there is any ETA on getting the VS2017 integration working.

Thank you.