blocks|key|189820|text|您的测试类必须为public+(但您的测试方法可以是private和/或static)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|189821|189822|出于效率的原因，xUnit作者选择在运行器中搜索测试类时不使用BindingFlags.NonPublic+(MSIL元数据表不会对private(/internal)类进行相同程度的索引，因此在反射可以实现的相对效率方面存在显著的性能差异)。|189823|由于上面的原因，你的class+is+classis意味着它不会被提取。|189824|测试方法是private++static+这一事实在设计上是很好的，因为1.0已经同时支持了这两个方面。|189825|请注意，Visual+Studio扩展、xunit.console.exe+(和图形用户界面)、xunit+MSBuild任务、Resharper和CodeRush在遵守这一点上都是一致的(尽管可以说，当测试类(即可能间接包含Fact-derived注释的类)为private时，它们可以做更多的标记，特别是后两者)。|189826|TestDriven.net运行您的测试的原因是，TestDriven.net的作者已经投入了大量的精力来使其正常工作。它在内部使用一个特殊的test+Runner包装器/填充程序(称为Adhoc+Runner)来运行您的测试。请注意，该方法实际上不是通过xUnit.net运行器运行的，因此您放在测试上的任何有副作用的属性都不会被触发。|189827|值得注意的是，NUnit+(以及我非常确定的MSTest)确实使用了私有反射，因此会在private类中选择测试，这可能就是为什么您以前不需要担心它的原因。|189828|注意:由此带来的一个副作用/技巧是，您可以创建一个测试类private，作为对测试类和任何嵌套类中的所有测试执行Skipping的一种快捷方式。(可悲的是，在这个星球上，无意中使用这种方法的案例远远超过了有意使用这种方法的案例！)|189829|entityMap^0|5|12|8|6|Q|7|10|6|0|0|0|3E|V|M|1U|7|23|8|0|0|F|G|2|J|H|A|5|J|5|0|0|C|E|6|L|V|5|7|E|6|0|0|4F|K|H|1C|5|35|4|3N|7|0|0|4P|0|0|26|17|7|0|0|37|S|7|1K|4|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|D]|$9|12|A|13|B|D]|$9|14|A|15|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|16|8|@]|E|@]|F|$]]|$1|H|3|I|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|D]|$9|1C|A|1D|B|D]|$9|1E|A|1F|B|D]]|E|@]|F|$]]|$1|J|3|K|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]|$9|1N|A|1O|B|D]|$9|1P|A|1Q|B|D]]|E|@]|F|$]]|$1|L|3|M|5|6|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|D]|$9|20|A|21|B|D]]|E|@]|F|$]]|$1|N|3|O|5|6|7|22|8|@$9|23|A|24|B|C]|$9|25|A|26|B|D]|$9|27|A|28|B|D]|$9|29|A|2A|B|D]|$9|2B|A|2C|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|6|7|2D|8|@$9|2E|A|2F|B|C]]|E|@]|F|$]]|$1|R|3|S|5|6|7|2G|8|@$9|2H|A|2I|B|C]|$9|2J|A|2K|B|D]]|E|@]|F|$]]|$1|T|3|U|5|6|7|2L|8|@$9|2M|A|2N|B|C]|$9|2O|A|2P|B|D]|$9|2Q|A|2R|B|D]]|E|@]|F|$]]|$1|V|3|-4|5|6|7|2S|8|@]|E|@]|F|$]]]|W|$]]

TL;DR your Test Classes must be <code>public</code> (but your Test Methods can be <code>private</code> and/or <code>static</code>)

<hr>

For reasons of efficiency, the xUnit authors have opted to not use <code>BindingFlags.NonPublic</code> when searching for Test Classes in the runner (the MSIL metadata tables don't index <code>private</code>(/<code>internal</code>) classes to the same degree hence there is a significant performance difference in the relative efficiency that Reflection can thus achieve). 

As a result of the above, the fact that your <code>class</code> is <code>private</code> means it doesn't get picked up.

The fact that the Test Method is <code>private</code> and <code>static</code> is fine - xUnit by design since 1.0 has supported both those aspects.

Note that the Visual Studio xUnit Runner extension, <code>xunit.console.exe</code> (and the GUI), the <code>xunit</code> MSBuild task, Resharper and CodeRush are all consistent in honouring this (although arguably they [especially the latter two] could do more to flag when a Test Class (i.e. class [potentially indirectly] containing <code>Fact</code>-derived annoations) is <code>private</code>).

The reason TestDriven.net runs your test is that the Author of TestDriven.net has put great effort into making it Just Work. It internally uses a special Test Runner wrapper/shim (termed the Adhoc Runner) to run your test. Be aware that the method is actually not being run via the xUnit.net runner and hence any attributes you put on your test that have side effects will not be triggered.

Notably NUnit (and I'm pretty sure MSTest) do use private reflection [and hence pick up tests in <code>private</code> classes] which is probably why it never seemed an important thing for you to worry about before.

Note: A side effect / trick enabled by this is that you can make a Test Class <code>private</code> as a quick way of <code>Skip</code>ping all tests in a Test Class [and any nested classes]. (Sadly the cases on this planet of this being used unintentionally vastly outnumber the intentional cases of this though!)

blocks|key|190211|text|(正如@Kyle在另一个答案的评论中提到的那样)使用NuGet获取xUnit.dll并最终使用2.0.0版本(目前被标记为预发布，因为一些核心功能，如发现v1测试等尚未在该分支中实现)可能会导致相同的No+tests+found+to+run消息。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|190212|这种情况下的解决方案是在包管理器中选择稳定的版本(而不是包含预发布的)。|BOLD|190213|entityMap^0|2S|L|0|J|3|S|6|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|N|8|@$9|O|A|P|B|H]|$9|Q|A|R|B|H]]|D|@]|E|$]]|$1|I|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|J|$]]

(As referred to by @Kyle in the comments on the other answer) The same <code>No tests found to run</code> message can result from using NuGet to get xUnit.dll and ending up with version 2.0.0 (which is currently marked as prerelease as some core functionality like discovering of v1 tests etc. has yet to be implemented in that branch).

The resolution in this case is to select Stable Only versions (as opposed to Include Prerelease) in the NuGet package manager.

blocks|key|3023419|text|这个答案是针对VS2013的，但对于VS2012，步骤基本上是相同的。这适用于通过ReSharper's+unit+test+functionality运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3023420|3023421|安装Visual+Studio2013的xUnit.net运行器(请注意以管理员身份运行Visual+Studio，否则在以非管理员身份运行xUnit.net时可能无法运行测试)：|ordered-list-item|3023422|3023423|a.在Visual+Studio2013中，转至Tools+->+Extensions+and+Updates+->+Online|3023424|b.搜索Visual+Studio2012和2013的xUnit.net+runner|3023425|c.然后下载(安装)它。如果从VS2012升级到VS2013，建议先卸载，然后再重新安装。|3023426|d.重启Visual+Studio.|3023427|3023428|如果安装了ReSharper，请安装xUnit.net测试运行器插件：|3023429|3023430|(注意:从ReSharper+2016.1开始，xunit+support+is+built+in+to+ReSharper，这意味着不再需要xunit插件。)|3023431|a.在Visual+Studio2013中，导航:+Resharper+->扩展管理器。|3023432|b.在左侧，选择Online。|3023433|c.搜索“xunit.net”。选择“xUnit.net测试支持”。单击Install。|3023434|d.重启Visual+Studio2013。|3023435|3023436|“清洁”解决方案|3023437|3023438|a.在IDE的“解决方案资源管理器”中，右击该解决方案，然后选择“清理”。|3023439|b.重新编译。|3023440|c.现在，当右键单击[Fact]属性时，选择Resharper的“Run+Unit+Tests”(相对于默认的“Run+Tests”)|style|CODE|3023441|使用XUnit运行疑难解答：|BOLD|3023442|3023443|如果使用XUnit运行事实测试的问题仍然存在，则可能需要从以下任意/所有文件夹中手动删除xUnit包(查看xunit+DLL的内容，如果找到，则删除xUnit文件夹)：|unordered-list-item|3023444|3023445|-+`C:\Program+Files+(x86)\Microsoft+Visual+Studio+12.0\Common7\IDE\Extensions\`|code-block|syntax|javascript|3023446|-+`C:\Users\<username>\AppData\Local\Microsoft\VisualStudio\12.0\Extensions\`|3023447|对于|3023448|+ReSharper，请尝试卸载并重新安装xunitcontrib库(xUnit.net测试支持)。我注意到有一次卸载时，一些错误消息闪烁过去。我一度抓取了一个屏幕截图，它列出了：|3023449|3023450|-+Access+to+the+path+`C:\Users\<username>\AppData\Local\JetBrains\ReSharper\vAny\packages\xunitcontrib.1.3.0\ReSharper\v8.1\plugins\xunit.dll`+is+denied.
-+...+and+the+same+for+the+other+DLLs+in+that+directory|3023451|要解决此问题，请在从Visual+Studio卸载后删除C:\Users\<username>\AppData\Local\JetBrains\ReSharper\vAny\packages\xunitcontrib.1.3.0\目录，然后以非管理员身份运行Visual+Studio，并通过ReSharper+(Resharper+->扩展管理器)重新安装|3023452|entityMap|0|LINK|mutability|MUTABLE|url|http://www.jetbrains.com/resharper/features/unit_testing.html|1|https://blog.jetbrains.com/dotnet/2016/04/14/resharper-ultimate-2016-1-is-released/^0|15|Z|0|0|0|0|0|0|0|0|0|0|0|0|O|12|1|0|0|0|0|0|0|0|0|0|0|A|6|0|9|5|0|0|0|0|0|0|0|0|0|0|S|2F|0^^$0|@$1|2|3|4|5|6|7|2E|8|@]|9|@$A|2F|B|2G|1|2H]]|C|$]]|$1|D|3|-4|5|6|7|2I|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|2J|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|2K|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|2L|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|2M|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|2N|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|2O|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|2P|8|@]|9|@]|C|$]]|$1|R|3|S|5|G|7|2Q|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|2R|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|2S|8|@]|9|@$A|2T|B|2U|1|2V]]|C|$]]|$1|W|3|X|5|6|7|2W|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|2X|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|2Y|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|2Z|8|@]|9|@]|C|$]]|$1|14|3|-4|5|6|7|30|8|@]|9|@]|C|$]]|$1|15|3|16|5|G|7|31|8|@]|9|@]|C|$]]|$1|17|3|-4|5|6|7|32|8|@]|9|@]|C|$]]|$1|18|3|19|5|6|7|33|8|@]|9|@]|C|$]]|$1|1A|3|1B|5|6|7|34|8|@]|9|@]|C|$]]|$1|1C|3|1D|5|6|7|35|8|@$A|36|B|37|1E|1F]]|9|@]|C|$]]|$1|1G|3|1H|5|6|7|38|8|@$A|39|B|3A|1E|1I]]|9|@]|C|$]]|$1|1J|3|-4|5|6|7|3B|8|@]|9|@]|C|$]]|$1|1K|3|1L|5|1M|7|3C|8|@]|9|@]|C|$]]|$1|1N|3|-4|5|6|7|3D|8|@]|9|@]|C|$]]|$1|1O|3|1P|5|1Q|7|3E|8|@]|9|@]|C|$1R|1S]]|$1|1T|3|1U|5|1Q|7|3F|8|@]|9|@]|C|$1R|1S]]|$1|1V|3|1W|5|6|7|3G|8|@]|9|@]|C|$]]|$1|1X|3|1Y|5|1M|7|3H|8|@]|9|@]|C|$]]|$1|1Z|3|-4|5|6|7|3I|8|@]|9|@]|C|$]]|$1|20|3|21|5|1Q|7|3J|8|@]|9|@]|C|$1R|1S]]|$1|22|3|23|5|6|7|3K|8|@$A|3L|B|3M|1E|1F]]|9|@]|C|$]]|$1|24|3|-4|5|6|7|3N|8|@]|9|@]|C|$]]]|25|$26|$5|27|28|29|C|$2A|2B]]|2C|$5|27|28|29|C|$2A|2D]]]]

This answer is for VS 2013, but the steps are essentially the same for VS 2012. This applies for running via <a href="http://www.jetbrains.com/resharper/features/unit_testing.html" rel="nofollow noreferrer">ReSharper's unit test functionality</a>.
<ol>
<li>Install the xUnit.net runner for Visual Studio 2013 (be careful running Visual Studio as an Administrator, or the tests may not run when running the IDE as a non-Admin):
a. From within Visual Studio 2013, go to Tools -&gt; Extensions and Updates -&gt; Online
b. Search for xUnit.net runner for Visual Studio 2012 and 2013
c. Then download (install) it. If upgrading to VS 2013 from VS 2012, it is suggested that this be uninstalled, and then re-installed.
d. Restart Visual Studio.
</li>
<li>If ReSharper is installed, install the xUnit.net test runner plugin :
(NOTE: Since ReSharper 2016.1, <a href="https://blog.jetbrains.com/dotnet/2016/04/14/resharper-ultimate-2016-1-is-released/" rel="nofollow noreferrer">xunit support is built in to ReSharper</a>, meaning the xunit plugin is no longer required.)
a. In Visual Studio 2013, Navigate: Resharper -&gt; Extension Manager.
b. On the left, select Online.
c. Search for “xunit.net”. Select the “xUnit.net Test Support”. Click Install.
d. Restart Visual Studio 2013.
</li>
<li>“Clean” the solution
a. In the IDE, in Solution Explorer, right-click the solution, and choose “Clean”.
b. Re-compile.
c. Now, when right-clicking a <code>[Fact]</code> attribute, select Resharper’s “Run Unit Tests” (as opposed to the default “Run Tests”)
</li>
</ol>
Troubleshooting running with XUnit:
<ul>
<li>If problems running the [Fact] tests with XUnit persist, it might
be necessary to manually remove the xUnit package from any/all of the
following folders (review content for the xunit DLLs, then delete
xUnit folder if found):
<ul>
<li><code>C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\</code>
</li>
<li><code>C:\Users\&lt;username&gt;\AppData\Local\Microsoft\VisualStudio\12.0\Extensions\</code>
</li>
</ul>
</li>
<li>As for ReSharper, try un-installing and re-installing the
xunitcontrib library (xUnit.net Test Support). I have noticed once
when un-installing, some error messages flashing past. I grabbed a
screen-shot at one point, and it listed:
<ul>
<li>Access to the path
<code>C:\Users\&lt;username&gt;\AppData\Local\JetBrains\ReSharper\vAny\packages\xunitcontrib.1.3.0\ReSharper\v8.1\plugins\xunit.dll</code>
is denied.</li>
<li>... and the same for the other DLLs in that directory</li>
</ul>
</li>
</ul>
To resolve this, delete the <code>C:\Users\&lt;username&gt;\AppData\Local\JetBrains\ReSharper\vAny\packages\xunitcontrib.1.3.0\</code> directory after uninstalling from Visual Studio, then run Visual Studio as a non-administrator, and re-install via ReSharper (Resharper -&gt; Extension Manager)

blocks|key|189910|text|在我的例子中，为了查看任何测试，我必须完成以下步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|189911|(全部通过NuGet包管理器安装)|189912|通过以下链接将v2.0.50727|189913|Install+v2.0.50727|unordered-list-item|189914|
|189915|Navigate+http://xunit.github.io/docs/running-tests-in-vs.html|offset|length|189916|
安装到|189917|，然后按照文档中列出的步骤进行操作：http://xunit.github.io/docs/running-tests-in-vs.html|ordered-list-item|189918|189919|我正在使用Visual+Studio+2013+Premium。(未安装Resharper)|189920|entityMap|0|LINK|mutability|MUTABLE|url|http://xunit.github.io/docs/running-tests-in-vs.html|1^0|0|0|0|0|0|9|1G|0|0|0|I|1G|1|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|18|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|19|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|1A|8|@]|9|@$M|1B|N|1C|1|1D]]|A|$]]|$1|O|3|P|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1F|8|@]|9|@$M|1G|N|1H|1|1I]]|A|$]]|$1|T|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1K|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]|14|$5|Z|10|11|A|$12|13]]]]

In my case, in order to see any tests, I had to complete the following steps:

(All installed through NuGet Package Manager)

<ol>
<li>Install <code>xUnit</code> v2.0.50727</li>
<li>Install <code>xUnit.extensions</code> v2.0.50727</li>
<li>Navigate to the following link and follow the steps outlined in the documentation: <a href="http://xunit.github.io/docs/running-tests-in-vs.html" rel="nofollow">http://xunit.github.io/docs/running-tests-in-vs.html</a></li>
</ol>

I'm using Visual Studio 2013 Premium. (Resharper NOT installed)

blocks|key|2810922|text|对我来说，我的测试类和测试方法名的组合太长了；xUnit似乎对这种组合有一些限制。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2810923|只要缩短测试方法的名称，xUnit就可以发现这一项测试。缩短整个类的名称允许xUnit发现类中的所有测试。|2810924|类名%2B方法名的阈值显示为172个字符。|2810925|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

For me, the combination of my test class and test method names were too long; xUnit appears to have some cap on this combination.

Shortening the name of just the test method allowed xUnit to discover that single test. Shortening the name of the entire class allowed xUnit to discover all tests in the class.

Threshold of class name + method name appears to be 172 characters.

blocks|key|3023673|text|来自http://xunit.github.io/docs/getting-started-desktop.html#run-tests-visualstudio|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3023674|3023675|如果您在发现或运行测试时遇到问题，您可能是Visual+Studio中损坏的运行器缓存的受害者。若要清除此缓存，请关闭Visual+Studio的所有实例，然后删除文件夹%25TEMP%25\VisualStudioTestExplorerExtensions。还要确保您的项目仅链接到Visual+Studio+runner+NuGet包(xunit.runner.visualstudio)的单个版本。|blockquote|3023676|3023677|entityMap|0|LINK|mutability|MUTABLE|url|http://xunit.github.io/docs/getting-started-desktop.html#run-tests-visualstudio^0|2|27|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|V|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

From <a href="http://xunit.github.io/docs/getting-started-desktop.html#run-tests-visualstudio">http://xunit.github.io/docs/getting-started-desktop.html#run-tests-visualstudio</a>:

<blockquote>
 If you're having problems discovering or running tests, you may be a
 victim of a corrupted runner cache inside Visual Studio. To clear this
 cache, shut down all instances of Visual Studio, then delete the
 folder %TEMP%\VisualStudioTestExplorerExtensions. Also make sure your
 project is only linked against a single version of the Visual Studio
 runner NuGet package (xunit.runner.visualstudio).
</blockquote>

blocks|key|189967|text|我在.NET核心中遇到这个问题已经有一段时间了，因为测试类或测试方法没有被发现。以下修复方法适用于我：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|189968|189969|打开命令提示符窗口。|ordered-list-item|189970|切换到运行以下命令的项目：|189971|189972|dotnet+build|189973|注意:从Visual+Studio.NET生成将不起作用！<<<<<<<<<<<+重要！|offset|length|style|BOLD|189974|189975|运行测试:测试-->运行-->测试全部-+CTRL%2BR+%2BA+(这将发现新测试，但不运行新测试。|189976|再次运行测试。|189977|189978|entityMap^0|0|0|0|0|0|0|15|3|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|11|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@$M|15|N|16|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|R|3|S|5|E|7|18|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|19|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|X|$]]

I've been having this issue with .NET Core for a while now where a test class or a test method is not being discovered. The following fix works for me:

<ol>
<li>Open a command prompt window.</li>
<li>Change to the project directory.</li>
<li>Build the project running the following command:

<pre><code>dotnet build
</code></pre></li>
</ol>

NOTE: Building from Visual Studio.NET will not work! &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt; IMPORTANT!

<ol start="4">
<li>Run the tests: Test --> Run --> Test All - CTRL+R +A (this will discover the new test(s) - but not run the the new test(s).</li>
<li>Run the tests again.</li>
</ol>

blocks|key|192552|text|我在VS2017+RC，.NET+Core1.1项目中也遇到了同样的问题。更新xunit.runner对我很有效，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|192553|Install-Package+xunit.runner.visualstudio|code-block|syntax|javascript|192554|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I had the same issue in VS2017 RC, .NET core 1.1 project. Updating xunit.runner worked for me,

<pre><code>Install-Package xunit.runner.visualstudio
</code></pre>

I have a xUnit.net Test as follows:

<pre class="lang-cs prettyprint-override"><code>static class MyTestClass
{
 [Fact]
 static void MyTestMethod() 
 {
 }
}
</code></pre>

The xUnit plugin for VS 2012 says:

<blockquote>
 No tests found to run.
</blockquote>

TestDriven.net runs it fine <a href="http://www.testdriven.net/quickstart.aspx#Ad%20Hoc%20Tests" rel="noreferrer">but mentions something about Ad hoc</a>:

<blockquote>
 1 passed, 0 failed, 0 skipped (see 'Task List'), took 0.47 seconds (Ad hoc)
</blockquote>

TeamCity, <code>xunit.gui.exe</code> and <code>xunit.console.exe</code> and Visual Studio also can't find <code>TestMethod</code>

(I've got <code>xunit.runner.visualstudio</code> installed and VS is seeing some tests.)

What gives?

Why is the xUnit Runner not finding my tests

Visual Studio

包管理器

我有一个xUnit.net测试，如下所示：static class MyTestClass{    [Fact]    static void MyTestMethod()     {    }}VS 2012的xUnit插件说：找不到要运行的测试。TestDriven.net运行得很好， 1通过，0失败，0跳过(请参...

问为什么xUnit运行器找不到我的测试
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么xUnit运行器找不到我的测试EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么xUnit运行器找不到我的测试
EN