运行包含在.NET Standard 1.6库中的xunit测试

Question

I just created a netstandard library in Visual Studio 2017 and added references to xunit and xunit.runner.visualstudio , but the VS Test Explorer and Resharper 2017 EAP 3 are not recognizing any tests. I've seen: Unit testing a .NET Standard 1.6 library but project.json is gone and csproj is back in place.

What do I have to do, to be able to run the unit tests included in a netstandard library?

Library.csproj

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netstandard1.6</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="xunit" Version="2.2.0" />
    <PackageReference Include="xunit.runner.visualstudio" Version="2.2.0" />
  </ItemGroup>
</Project>

Test.cs

namespace ClassLibrary2
{
    public class Class1
    {
        [Fact]
        public void RescharperShouldRunTest()
        {
            Assert.True(true);
        }
    }
}

Edit

Thanks to the answers I made some progress.

Adding

<PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0" />  
<!-- ... and ...  --> 
<ItemGroup>
    <Service Include="{82a7f48d-3b50-4b1e-b82e-3ada8210c358}" />
</ItemGroup>

did have no impact. Only if I change the TargetFramework to netcoreapp1.1 VS discovered the test and could run them. With netstandard1.6 the Test Explorer remains empty. But I don't want a netcore app. I want a .NET standard library.

Answer 1

If you run dotnet new xunit you will see an additional reference included.

<PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0" />

I have found the same outcome in the current IDE tooling. You can however run the tests on the commandline using

dotnet test -l "trx"

I'm trying to target netstandard1.5;net452 but only the net452 tests are run, not the netstandard1.5 tests.

Answer 2

Unfortunately you are correct in that class libraries (Or .net standard libraries) are not made to run unit tests. Infact many tutorials you find on the web (Such as this one : http://dotnetcoretutorials.com/2017/01/30/running-unit-tests-dotnet-test/ ) will talk you into creating a CONSOLE application and then deleting what you don't need.

I think the issue likely is why does your unit tests need to be in a .net standard library? If you are distributing a library that has associated unit tests, the tests themselves don't need to be in .net standard as nothing will be referencing them. And within your own solution, test assemblies that are to be run shouldn't be referenced from elsewhere.

Answer 3

I know this is an older question, but I have had the same problem - writing xunit tests that run in the Visual Studio test runner and Xamarin.iOS/Droid . For netstandard what I ended up doing was creating a Unit test project that was .NET Core 2.0, creating the Xamarin.* test applications (and configuring them for unit), and creating a Shared project instead of netstandard library. This worked for me.

My test project structure is:

• Project.Tests.Droid (Droid UI project)
• Project.Tests.iOS (iOS UI project)
• Project.Tests.Unit (VS Unit test project)
• Project.Tests (shared project)

All my tests are in Project.Tests.

Answer 4

It is tricky, but doable, if you refer to the other answer as well as the sample project below,

https://github.com/lextm/sharpsnmplib/blob/master/Tests/Tests.NetStandard.csproj

Of course, some NuGet packages used in the sample have already been updated to stable.

The following are critical, <PackageReference Include="Microsoft.NET.Test.Sdk"> <Version>15.0.0-preview-20170125-04</Version> </PackageReference> <PackageReference Include="xunit"> <Version>2.2.0-beta5-build3474</Version> </PackageReference> <PackageReference Include="xunit.runner.visualstudio"> <Version>2.2.0-beta5-build1225</Version> </PackageReference> The project that contains unit test cases must be a console app targeting .NET Core.