blocks|key|2309562|text|.NET标准库不包含执行所需的组件。它只定义了执行模式。当部署到特定的计算机/处理器体系结构时，代码必须知道要在哪个指令集上执行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2309563|这就是.NET框架和.NET核心发挥作用的地方。.NET框架包含Microsoft操作系统支持的指令集的执行详细信息。类似地，.NET核心包含用于本机不支持的其他体系结构的指令集。|2309564|要编写单元测试，您需要在.NET或.NET内核中创建一个新项目来执行代码。如果您想涵盖所有的基础，或者如果您有一些针对不同体系结构不同编译的二进制文件(考虑到第三方库)，那么您可能希望对多个发行版进行单元测试。|2309565|你的图书馆应该是一个独立的图书馆。在更新库以验证输入到库中的代码是否通过之前，应该执行单元测试。这样，任何在那之后使用这个库的人都会对它的工作充满信心。|2309566|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

A .NET Standard Library does not contain the necessary components for execution. It only defines the execution patterns. When you deploy to a specific machine / processor architecture, the code must know which instruction set to execute upon. 

This is where the .NET framework and .NET core come into play. The .NET framework contains execution details for instruction sets supported by the Microsoft Windows operating system. .NET core, similarly, contains the instruction set for additional architectures not natively supported by Windows.

To write Unit Tests, you need to create a NEW project, either in .NET or in .NET core, to execute your code. If you want to cover all your bases, or if you have some binaries that are compiled differently for different architectures (third party libraries come to mind) then you might want to unit test for multiple distributions. 

Your library should be a standalone library. Your unit tests should be executed before you update the library to validate that the code being entered into the library passes. That way anyone who uses the library after that can feel confident that it will work.

blocks|key|289475|text|编写针对.NETStandard的库单元测试是很棘手的，因为您必须根据您选择的.NETStandard版本的各种实现来测试您的代码。正如扎克·迪亚兹已经概述的那样，这是因为.NETStandard仅仅定义了在实际平台中实现的类型。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|289476|最常见的问题是不同平台(如.NETFramework、.NETCore、Mono等)在实现方面的差异。然而，不同版本的平台之间的实现也存在差异，它们可能会影响库在上述平台上的工作方式(参见这个例子)。|289477|这就是为什么在实现所选版本的.NETStandard的平台的最低版本上运行您的测试并没有完全减少它的原因。您必须考虑库可以一起使用的所有运行时。|289478|一般来说，您有两个选项来解决这个问题。|289479|选项1|style|BOLD|289480|使用多靶点为所有有效运行时构建单元测试项目。这也意味着您必须为您的单元测试项目拥有一组非常大的目标框架，在发布平台的新版本时必须对其进行扩展。|289481|如果您想要涵盖所有相关的场景，那么您将拥有数十个目标框架和正在构建的单元测试项目的相同多个版本。让我们假设这会很快失控。|289482|选项2|289483|使用一个能够通过设计实际处理.NETStandard的单元测试平台。构建.NETStandard的单元测试并让这些测试在匹配的运行时上执行将降低测试项目的复杂性。|289484|到目前为止，大多数单元测试平台都无法做到这一点，您只能使用选项1。适合这种方法并真正解决您的问题的是Nuclear.Test。|289485|请注意，Nuclear.Test需要.NETStandard+2.0，并且在其当前版本中只处理.NETFramework和.NETCore。不过，这可能会发生变化，我正在努力将所需的.NETStandard版本减少到1.0，并包括Mono和UWP的测试人员。|blockquote|289486|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/58273939/9595496|1|https://github.com/MikeLimaSierra/Nuclear.Test/blob/master/README.md#example-5|2|https://stackoverflow.com/a/48885500/9595496|3|https://dotnet.microsoft.com/platform/dotnet-standard#versions|4|https://github.com/MikeLimaSierra/Nuclear.Test^0|1W|6|0|0|2M|4|1|0|0|0|0|3|0|2|3|2|0|L|7|3|0|0|3|0|0|T|3|1E|C|4|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@$A|1H|B|1I|1|1J]]|C|$]]|$1|D|3|E|5|6|7|1K|8|@]|9|@$A|1L|B|1M|1|1N]]|C|$]]|$1|F|3|G|5|6|7|1O|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|1P|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|1Q|8|@$A|1R|B|1S|L|M]]|9|@]|C|$]]|$1|N|3|O|5|6|7|1T|8|@]|9|@$A|1U|B|1V|1|1W]]|C|$]]|$1|P|3|Q|5|6|7|1X|8|@]|9|@$A|1Y|B|1Z|1|20]]|C|$]]|$1|R|3|S|5|6|7|21|8|@$A|22|B|23|L|M]]|9|@]|C|$]]|$1|T|3|U|5|6|7|24|8|@]|9|@]|C|$]]|$1|V|3|W|5|6|7|25|8|@$A|26|B|27|L|M]]|9|@$A|28|B|29|1|2A]]|C|$]]|$1|X|3|Y|5|Z|7|2B|8|@]|9|@]|C|$]]|$1|10|3|-4|5|6|7|2C|8|@]|9|@]|C|$]]]|11|$12|$5|13|14|15|C|$16|17]]|18|$5|13|14|15|C|$16|19]]|1A|$5|13|14|15|C|$16|1B]]|1C|$5|13|14|15|C|$16|1D]]|1E|$5|13|14|15|C|$16|1F]]]]

Writing unit tests for libraries targeting .NETStandard is tricky since you have to test your code against various implementations of your chosen version of .NETStandard.
As already outlined by <a href="https://stackoverflow.com/a/58273939/9595496">Zakk Diaz</a> this is due to the fact that .NETStandard merely defines types that are then implemented in actual platforms.

The most common problems are differences in implementation across various platforms like .NETFramework, .NETCore, Mono, etc.
However there are also differences in implementations across various versions of platforms that can mess with the way your library works on said platforms (see <a href="https://github.com/MikeLimaSierra/Nuclear.Test/blob/master/README.md#example-5" rel="nofollow noreferrer">this example</a>).

This is why running your tests on the lowest version of a platform that implements your chosen version of .NETStandard doesn't quite cut it.
You have to take all runtimes into account that your library could be used with.

In general you have two options to solve this issue.

Option 1

Use <a href="https://stackoverflow.com/a/48885500/9595496">multi targeting</a> to build your unit test project for all valid runtimes.
This also means that you have to have a very big set of target frameworks for your unit test project which will have to be extended whenever new versions of a platform are released.

If you want to cover all relevant scenarios then you'll have <a href="https://dotnet.microsoft.com/platform/dotnet-standard#versions" rel="nofollow noreferrer">dozens of target frameworks</a> and just as many versions of your unit test project being built.
Let's just assume that this can get out of hand quickly.

Option 2

Use a unit testing platform that can actually handle .NETStandard by design.
Building your unit tests for .NETStandard and having those tests execute on matching runtimes will reduce complexity of your test project.

As of today, most unit testing platforms can't do any of this and you're stuck with Option 1.
The one that fits this approach and actually solves your problem is <a href="https://github.com/MikeLimaSierra/Nuclear.Test" rel="nofollow noreferrer">Nuclear.Test</a>.

<blockquote>
 Please note that Nuclear.Test requires .NETStandard 2.0 and only handles .NETFramework and .NETCore in its current release. This is subject to change however and i'm working on reducing the required version of .NETStandard to 1.0 and include test workers for Mono and UWP as well.
</blockquote>

blocks|key|2309711|text|有一个简单的旁路，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2309712|用3个项目创建解决方案：|2309713|"Demo.NetStandard"|ordered-list-item|offset|length|style|BOLD|2309714|您的.Net标准库项目|blockquote|2309715|"Demo.NetFramework.LinkedToStandard"|2309716|新的.Net框架库项目，并复制和粘贴为链接所有.Net标准文件|2309717|"Demo.Tests"|2309718|新的.Net框架测试项目，并添加引用>+"Demo.NetFramework.LinkedToStandard“|2309719|这样，您就可以将代码直接写入.NetStandard文件，并将其作为.NetFramework代码进行测试。|2309720|entityMap^0|0|0|0|I|0|0|0|10|0|G|5|0|0|C|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|11|8|@$G|12|H|13|I|J]]|9|@]|A|$]]|$1|K|3|L|5|M|7|14|8|@]|9|@]|A|$]]|$1|N|3|O|5|F|7|15|8|@$G|16|H|17|I|J]]|9|@]|A|$]]|$1|P|3|Q|5|M|7|18|8|@$G|19|H|1A|I|J]]|9|@]|A|$]]|$1|R|3|S|5|F|7|1B|8|@$G|1C|H|1D|I|J]]|9|@]|A|$]]|$1|T|3|U|5|M|7|1E|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1F|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|Y|$]]

There is an easy bypass,
Create solution with 3 projects:
<ol>
<li>&quot;Demo.NetStandard&quot;</li>
</ol>
<blockquote>
your .Net Standard library project
</blockquote>
<ol start="2">
<li>&quot;Demo.NetFramework.LinkedToStandard&quot;</li>
</ol>
<blockquote>
new .Net Framework library project, and copy &amp; paste as link all .Net Standard files
</blockquote>
<ol start="3">
<li>&quot;Demo.Tests&quot;</li>
</ol>
<blockquote>
new .Net Framework test project, and Add Reference &gt; &quot;Demo.NetFramework.LinkedToStandard&quot;
</blockquote>
This way you write the code straight into your .NetStandard files, and you test it as .NetFramework code.

So as far as I have been understanding from my research. A .net Standard Library can not be used on its own, so it needs to be tested through a different framework, either with .net Framework or .net Core <a href="https://stackoverflow.com/a/48885500/5966840">reference</a>. That's just how I interpreted it. 
 Now I am trying to create a Standard Library as I need it to be compatible on most devices as possible, the problem is I don't know how to create the unit tests correctly. Every time I create a MSTest Project I get the following error:

<blockquote>
 Test run will use DLL(s) built for framework .NETCoreApp,Version=v1.0 and platform X64. Following DLL(s) do not match framework/platform settings.
 Otchi.Ebml.Tests.dll is built for Framework 2.1 and Platform AnyCPU.
</blockquote>

I have experimented a lot with the different architectures and other settings, but nothing seems to work to remove that warning. Am I doing something incorrectly or is there a different, more suitable approach to creating unit tests for a Standard Library

How to correctly implement unit tests for .net Standard Library

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

因此，就我从我的研究中得到的理解而言。.net标准库不能单独使用，因此需要通过不同的框架进行测试，无论是使用.net框架还是使用.net核心。我就是这么解释的。现在我正在尝试创建一个标准库，因为我需要它在大多数设备上尽可能兼容，问题是我不知道如何正确地创建单元测试。每次创建MSTest项目时，我都会得到以下错误：测试运...

问如何正确实现.net标准库的单元测试
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何正确实现.net标准库的单元测试EN