No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again

Question

I am in the process of upgrading our existing solution to .Net 4.6.1 and have been unable to get our unit tests to run during a server build. Locally they run as expected and flipping the framework version back to .Net 4.5.1 makes them run again on the server.

I am getting the following error:

No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

I have reproduced the problem in a simpler setup:

Solution with a single C# Unit Test project with two tests (one failing, one passing).
XAML build definition using the Default Template (TfvcTemplate.12.xaml)
TFS 2015 Update 1 XAML build server with Visual Studio Enterprise 2015 Update 1 installed (have six similar servers and all produce the same result)

According to Brian Harry from Microsoft, this is bug they are currently investigating. It should be fixed in Update 2, and a temporary workaround should be posted later. Source: [link](http://blogs.msdn.com/b/bharry/archive/2015/11/30/vs-2015-update-1-and-tfs-2015-update-1-are-available.aspx#10665420) — Tore Østergaard, Jan 21 '16 at 09:33
I have the same problem for .Net 3.5 SP1 in Visual Studio 2013 Update 5. — Andrey Bushman, Jul 13 '16 at 09:32
@AndreyBushman: The error might be in 2013U5 too as it was released together with 2015RTM. But the workaround should work in your case too. — Tore Østergaard, Jul 21 '16 at 11:39
I had a similar problem, the workaround was simply in vs, under the test settings, to select the right default processer (32/64) bit, and no keep the engine runnig. (vs 2017.x) — kfn, Jun 24 '18 at 10:32

score 79 · Answer 1 · edited Jun 26 '18 at 14:55

79

You can try to change your default processor architecture in your Test Setting from X86 to X64. In my case this was the problem.

This happens if the platform target of your project under test is set to x64.

edited Jun 26 '18 at 14:55

Alex AIT

17,361
3
36
73

answered May 28 '18 at 18:29

rubeonline

1,230
10
18

This solved it for me. In my case, both the project being tested and the test project were set to x86. Tests were disoverable but failed to run. After I changed it to Any CPU, tests ran. – datchung Aug 15 '19 at 19:50
I just had the same problem and this resolved it. I am also quite suspicious that this may have had a bad nego-synergistic effect on my main project references, which suddenly stopped loading a particular DLL, but have not conclusively determined this nasty side effect. – Allen Mar 21 '20 at 16:01
Worked for me too, except that the menu was Test -> Processor Architecture for AnyCPU projects then select X64 – Nick Jun 08 '23 at 06:24

Nick Rubino · Answer 2 · 2019-01-22T19:35:16.097

72

My build was not finding the tests either. My setup and solution for finding the tests are as follows.

I use VSTS (Visual Studio Team Services) and have a build that is configured to refresh the NUGET packages on every build. I am using NUnit and found that running the following NUGET command (from the package manager console in Visual Studio) to add NUnitTestAdapter library to my test project and the checking in the packages.config made the tests run in my VSTS build.

Install-Package NUnitTestAdapter

As Maurice mentions in the Comment to this post for NUnit3 use the following NUGET package (Look for other utils on the link. i.e: dotnet CLI and Paket CLI)

Install-Package NUnit3TestAdapter

Hope this helps.

edited Jan 22 '19 at 19:35

answered Apr 13 '17 at 16:16

Nick Rubino

965
7
9

11

I'm also currently using VSTS. As adviced I added NUnit3TestAdapter (since I'm using NUnit 3.8.1) and this solution solved my problem. Thank you :-) – Maurice Klimek Oct 11 '17 at 06:53
1

Install-Package NUnit3TestAdapter solved my issue :) – Bimal Das Dec 15 '18 at 06:23

score 55 · Answer 3 · edited Oct 29 '20 at 14:42

55

In my case, I had to:

Convert test project to netcore 2.0 (was netstandard 2.0)
Add nuget package xunit.runner.visualstudio

Reference: http://www.neekgreen.com/2017/11/20/xunit-no-test-is-available/

edited Oct 29 '20 at 14:42

Tim

5,435
7
42
62

answered Apr 10 '18 at 19:01

scrat.squirrel

3,607
26
31

3

same issue was with me. I am using xunit with .net core – Amna Apr 16 '18 at 07:57
This also worked for me in Visual Studio 2017 with xunit and .NET Core 2.1. – Thorkil Værge Jul 19 '18 at 20:00
5

in my case was a .net 4.6.1 project so the only thing missing was the xunit runner. Installed it and worked. – Juan Feb 20 '19 at 18:10
2

Same as Juan. Only the runner package was missing. Running this in the package manager for the test project solved it: install-package xunit.runner.visualstudio – Premil Jun 02 '20 at 16:05
Confirmed. Accidentally removed the runner.visualstudio nuget package (keeping the xunit one). Re-introducing it fixed this problem. Thanks! – JohannSig Feb 18 '21 at 22:25

score 18 · Answer 4 · answered Apr 18 '18 at 07:58

18

I'm using MSTest. For me, it was version missmatch and missing another dependent package-

1) My package folder contains only MSTest.TestFramework.1.2.1 package. In my project file(.csproj) the reference in Target Name was MSTest.TestAdapter.1.2.0 package which was not present in package folder. My packages.config has also reference of MSTest.TestFramework.1.2.0 .

2) So I installed MSTest.TestAdapter.1.2.0 from nuget package manager and align MSTest.TestFramework version to 1.2.0 in project and package file. Finally I add Microsoft.VisualStudio.TestPlatform.TestFramework and Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions in the reference.

Then everything was OK. Hope this help someone.

answered Apr 18 '18 at 07:58

quasar

404
6
17

I bumped into this with .Net 4.6.1 VS2017. I ended up rolling back to 1.2.0 - definitely make sure you dont have two different versions in your packages folder or in source control. – Jeremy Thompson May 09 '18 at 04:26
5

Mine appeared to find the tests, but yes, missing "MSTest.TestAdapter" was the real issue. No nice errors or warning (VS2017 15.8). All looked good except no tests were found, despite appearing in the test explorer..... So when I did "install-package MSTest.TestAdapter" suddenly my tests ran as expected. Thanks MS - 3 hours wasted........... – James Joyce Jun 06 '18 at 15:22
2

Installing the MSTest.TestAdapter 1.4.0 did it for me in VS 2019. I only wasted 30 minutes thanks to you. – furman87 Aug 19 '19 at 19:54

score 11 · Answer 5 · answered Oct 31 '18 at 19:58

11

I got this error and was able to resolve it.

I use Visual Studio Professional 2017
In VS, I navigated to Tools --> Extensions And Updates
At the top of the menu, I'd noticed that my NUnit adapter was disabled
I clicked the [Enable] button
I was able to initiate tests without errors.

answered Oct 31 '18 at 19:58

J Wood

121
1
3

Yes! And don't forget to restart Visual Studio. That was required for me. – Michael Levy Nov 28 '18 at 16:34
"At the top of the menu" what does that mean? – Sean Kendle Feb 23 '19 at 23:05
1

@SaiyajinGohan. After you complete step 2, the "Extensions and Updates" window appears. At the top of this window, I saw the NUnit adapter was disabled. Hope this clarifies.... – J Wood Feb 25 '19 at 02:36
Thanks for that, I still couldn't get this working with the project I was working on. Luckily it was a test project and the next one worked. Still a mystery as to why. – Sean Kendle Feb 25 '19 at 17:23

score 9 · Answer 6 · edited Aug 15 '20 at 09:24

9

I fixed this problem by reinstalling all testing related NuGet packages for the project: Xunit, Xunit.runner.vistualstudio, Microsoft.Net.Test.Sdk

edited Aug 15 '20 at 09:24

Neuron

5,141
5
38
59

answered Nov 28 '18 at 10:19

n.sh

347
4
19

score 7 · Answer 7 · edited Aug 15 '20 at 09:23

7

Install Nunit and NUnitTestAdapter latest version from NUGET package.
Go to -> Test -> Test Settings -> Default processor architecture -> Change to X64
Build the solution.
This will resolve Run Test and Debugger issue in unit testing and it will start working.

edited Aug 15 '20 at 09:23

Neuron

5,141
5
38
59

answered Nov 29 '18 at 08:47

Karthikeyan Nandagopalan

71
1
2

This actually worked for me after banging my head in so many directions and suggestions. – rajibdotnet Sep 03 '20 at 14:45

score 6 · Answer 8 · answered Apr 05 '18 at 13:48

6

This problem surfaces for Visual Studio 2017 again. Most likely another bug but the same outcome.

One workaround that seems to work is to uninstall Microsoft Visual Studio 2017 Remote Debugger from the affected machine.

answered Apr 05 '18 at 13:48

Csapi007

133
1
2
6

score 5 · Answer 9 · edited Jun 20 '20 at 09:12

5

I ran into the same problem in VSTS with .Net 4.6.2. If you are seeing this from your VSTS console output, the workaround provided by @Sushil still works in VSTS and is needed. Unfortunately the "Test Assemblies" task provided by Microsoft passes, so you really don't even know there is a problem unless you check the output and find none of your tests actually executed!

edited Jun 20 '20 at 09:12

Community

1
1

answered Dec 15 '17 at 16:40

raterus

1,980
20
23

My problem was with (on-prem) TFS 2015 Update 1 and it was fixed with Update 2. I am not sure if the same issue exist/existed with VSTS. – Tore Østergaard Dec 15 '17 at 23:31

score 5 · Answer 10 · answered Jan 16 '19 at 21:09

I'll throw my solution onto the heap. In my case, I am adding a couple of projects to an existing solution along with Test projects for them. We're using MSTest. There was a previous UnitTest.testsettings file enabled on the solution that was causing compatibility issues.

Clicking on the settings file removed the check and the test run was successful for my tests.

score 4 · Answer 11 · edited Aug 15 '20 at 09:24

4

I faced the similar issue when tried nUnit in VS 2017 and it's not a core project. Installing NUnit3TestAdapter fixed the issue.

edited Aug 15 '20 at 09:24

Neuron

5,141
5
38
59

answered Nov 03 '18 at 14:01

Surendra Rayapati

108
1
10

score 4 · Answer 12 · answered Jun 12 '19 at 12:22

4

If you are running your tests inside docker using multistage building and tests aren't found. Make sure you copy all files not only project files like below Dockerfile section.

FROM mcr.microsoft.com/dotnet/core/sdk:2.2-stretch AS build
WORKDIR /src
COPY ["MainProject/FirstApp.csproj", "MainProject/"]
COPY ["TestProject/*", "TestProject/"]

RUN dotnet restore "TestProject/TestProject.csproj"
RUN dotnet build "TestProject/TestProject.csproj" -c Release
RUN dotnet test "TestProject/TestProject.csproj" -c Release

answered Jun 12 '19 at 12:22

Bassam Gamal

713
2
8
24

This did indeed bite me. I think the clue that this is happening is that it FINDS the unit test DLL, but it does NOT find any tests in it. I also found that putting this inline after your copy statements will let you inspect to see what WAS copied (here /app/tests is your target directory on the Docker image): RUN file="$(ls -al /app/tests)" && echo $file (see [this post for more info on echo](https://stackoverflow.com/a/34215313/97803) ) – David Yates Sep 11 '19 at 19:50

score 4 · Answer 13 · answered Oct 03 '20 at 06:33

I solved this issue by installing NUnit3TestAdapter NuGet into my project (https://www.nuget.org/packages/NUnit3TestAdapter/).

dotnet add package NUnit3TestAdapter --version 3.17.0

My .csproj file

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.7.1" />
    <PackageReference Include="NUnit" Version="3.12.0" />
    <PackageReference Include="NUnit3TestAdapter" Version="3.17.0" />
    <PackageReference Include="RestSharp" Version="106.11.7" />
  </ItemGroup>

</Project>

score 4 · Answer 14 · answered Oct 30 '20 at 11:43

This question is obviously being found by people with a range of scenarios, my answer will cover running XUnit tests on a .NET Core project using build pipeline on Azure DevOps but may help others too.

Ensure you have the XUnit test adapters installed from nuget as per this answer.
In the yaml for your build pipeline, add otherConsoleOptions: '/framework:.NETCoreApp,Version=v3.1' to the inputs of your VSTest@2 step (with the version number set to whatever version of .NET Core you are using). See this documentation for more info.
While this is not mandatory, I would recommend also adding failOnMinTestsNotRun: true so that the build pipeline will report a failure if zero tests are run.
If you run a build at this point, you may find that your tests run but the pipeline then gives the error The library 'hostpolicy.dll' required to execute the application was not found. You can solve this by changing your filter from the default **\*test*.dllto **\*test.dll (note the removed asterisk), or some other pattern which will match your test project's DLL. The reason for this is that XUnit places a file called testhost.dll in the output directory, as explained in this github issue.

If you are using the older pipelines which do not use yaml, the same options should be available. This answer covers adding the framework, I assume there will also be an option to "Fail the task if a minimum number of tests are not run" or something similar.

score 4 · Answer 15 · edited Nov 24 '21 at 00:28

4

I installed nunit3adapter package and it worked for me from my test log:
-->(NUnit3TestExecutor discovered 6 of 6 NUnit test cases using Current Discovery mode, Non-Explicit run)

edited Nov 24 '21 at 00:28

Furqan Rahamath

2,034
1
19
29

answered Nov 22 '21 at 14:51

SammieDyalnT

51
1

J-ho · Answer 16 · 2023-07-26T18:22:04.710

With net6.0 targetFramework I added these packages to .csproj-file:

<PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.10.0" />
<PackageReference Include="MSTest.TestAdapter" Version="2.2.5" />
<PackageReference Include="MSTest.TestFramework" Version="2.2.5" />

after which it started working. earlier versions may not be compatible with net6.0.

Do check the latest versions for the packages appropiate for your .NET version for example from nuget.org

score 3 · Answer 17 · answered Jun 14 '18 at 09:41

I fixed this by issue in VS 2017 & 4.6.2 test project with the following steps:

Remove references to Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll and extensions
Install the Microsoft.VisualStudio.QualityTools.UnitTestFramework.Updated nuget package

score 3 · Answer 18 · answered Sep 27 '18 at 15:58

Using .Net Core with a build pipeline in TFS 2017, my Visual Studio Test step was passing without actually executing any tests. Had to edit the step, "Advanced Execution Options" -> "Other console options" to include:

/framework:".NETCoreApp,Version=v2.0"

(That field also contains /platform:x64)

score 3 · Answer 19 · answered Oct 17 '18 at 15:07

3

Make sure that you've got the "Microsoft.NET.Test.Sdk" nuget installed.

answered Oct 17 '18 at 15:07

lordpansar

31
3

score 2 · Answer 20 · answered Feb 13 '19 at 15:32

2

This error can happen for async tests if you have the wrong return type. The return type should be Task, and not void.

answered Feb 13 '19 at 15:32

user3533716

491
7
14

MirrorBoy · Answer 21 · 2020-07-01T16:56:21.473

I use MSTest.

I installed from Nuget the latest version of MSTest.TestFramework and replaced OOB Remove references to Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll

Then Installed from neget the latest version of Microsoft.TestPlatform

It allowed me to run test with a command:

".\packages\Microsoft.TestPlatform.16.6.1\tools\net451\Common7\IDE\Extensions\TestPlatform\vstest.console.exe" "UnitTestProject1\bin\Debug\UnitTestProject1.dll" /logger:trx

But I got the same error. The root cause of the error that I didn't specify a test adapter which parses the assembly and finds tests.

Solution:

Install a nuget package "MSTest.TestAdapter"
Specify a test adapter in the end of a command:

/TestAdapterPath:".\packages\MSTest.TestAdapter.2.1.2\build_common"

Updating MSTest.TestAdapter (2.1.2->2.2.7) and MSTest.TestFramework (2.1.2->2.2.7) fixed it for me. Thanks! — Kevin, Oct 21 '21 at 03:14

score 2 · Answer 22 · answered Mar 28 '21 at 05:21

I have just been through this issue. It seems there may be a lot of causes for it. In my case, I was trying some codes and due to that, I renamed the project, removed it.. added it again... and all of a sudden, my single test stopped working and the Test output window was showing this error: "No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again" The Debug output was showing errors related to the platform: "Following dll(s) do not match current settings, which are .netframework , version 4.5 and platform X86."

Using VS 2019 v 16.8.0 Test project on .NET Framework 4.8 Configured to Debug/Any CPU

After trying a bunch of things, the solution was

Close Visual Studio
Rename the folder holding your solution. For example: C:\Git\Solution to C:\Git\Solution2
Open VS and load your solution. Try to run a test.

This worked for me, hope it works for you.

This worked for me. The error was strange after updating to latest version of VS2022. Installing any new libraries didnt help me. — tariq zafar, Oct 12 '22 at 22:33

score 1 · Accepted Answer · answered Jan 16 '16 at 08:08

1

This is a known issue for .Net 4.6 now.

Unable to run .Net 4.6.x unit tests as part of a XAML TFS Build with TFS 2015 UPdate1 Source:https://connect.microsoft.com/VisualStudio/feedback/details/2245723

Here is a similar question for you reference: Unable to run .Net 4.6 Unit tests of TFS 2015 XAML build server

answered Jan 16 '16 at 08:08

PatrickLu-MSFT

49,478
5
35
62

8

Hi Patrick. Both of the links you supply is cases opened by me, so I wouldn't trust them as reference ;-). – Tore Østergaard Jan 18 '16 at 07:56

Tore Østergaard · Answer 24 · 2016-07-21T11:40:08.220

This is just to recap the solution brought forward by @Sushil earlier.

This is a known issue in Team Foundation Server 2015 RTM + Update 1 and will be fixed in Update 2, reference.

There is a workaround described by @Sushil here, which includes adding a .runsettings file that forces the test runner to older .Net framework (please not that you have to specify it through the "Add/Edit Test Run" dialog as adding it directly in the build process editor will be ignored).

score 1 · Answer 25 · answered Sep 27 '18 at 14:12

1

I was getting a similar issue and noticed somehow an app.config file had been added to my test project. Removing this config file fixed it for me.

answered Sep 27 '18 at 14:12

thatWiseGuy

384
2
3
18

score 1 · Answer 26 · answered Sep 30 '18 at 08:02

1

In Visual Studio 2017 I just uninstall and reinstall NUnitTestAdapter or install new package like NUnitTestAdapter.WithFramework package and problem gone.

answered Sep 30 '18 at 08:02

Ali Yousefi

2,355
2
32
47

score 1 · Answer 27 · answered Nov 02 '18 at 21:45

1

I got this error because my Unit test class was not public.

Ex:

class ClientTests

Error in Output:

...\bin\Debug\Tests.dll] UTA001: TestClass attribute defined on non-public class ClientTests

Correction:

public class ClientTests

answered Nov 02 '18 at 21:45

Jared Beach

2,635
34
38

score 1 · Answer 28 · answered Jan 08 '19 at 23:00

I am having the same issue. I am using Visual Studio 2017 Community Edition.

I used these steps to successfully discover all my test cases and successfully run it:

First go to Extensions and Updates, install NUnit3 Test Adapter. If you already have, just enable it.
Restart your Visual Studio 2017, it will automatically prompt to
install your extension, if a prompt says to end task to continue
installing, just click "End Task".
After that, rebuild your Test Project and all test cases will now be identified and you can now start running your test cases.

score 1 · Answer 29 · answered Apr 08 '19 at 14:14

Found a way! Probably not the most orthodox but it did helped me out in a hurry:

Update the MSTest.TestAdapter and MSTest.TestAdapterFramework packages to the 1.4.0 from the Tools > NuGet Package Manager.
The clean the solution and run the tests again.

I don't think is anything particular with the version, but updating it certainly cleans whatever reference is bad in the solution/project.

score 1 · Answer 30 · answered Mar 10 '20 at 20:04

Try running vstest.console.exe with --diag:diag.txt and inspect the output. For me it was DLL load failures for test adapters from my working directory:

TpTrace Information: 0 : 14976, 1, 2020/03/10, 15:34:22.120, 57158093583, vstest.console.exe, AssemblyResolver.OnResolve: Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter: Failed to load assembly. Reason:System.IO.FileLoadException: Could not load file or assembly 'file:///C:\Directory\Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)

File name: 'file:///C:\Directory\Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter.dll' ---> System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.

I worked around this by adding <loadFromRemoteSources enabled="true"/> under <runtime> in vstest.console.exe.config

score 1 · Answer 31 · answered Dec 13 '22 at 17:26

I've recently run into this issue as well, and I can with some confidence state that it's not one covered by any of the other answers here.

I've recently been writing some F# modules that (for reasons) have signature files. Again, for reasons, I've had to put unit tests into the same module.

When an F# source file is 'covered' by a signature file, only the declared values are exported. Thus, you have to explicitly declare each and every test in the signature file as well, otherwise you'll get the error message in the OP.

score 1 · Answer 32 · answered Mar 28 '23 at 09:04

With NUnit3, in most cases all I had to do was to add

<PackageReference Include="NUnit3TestAdapter" Version="4.x.x" />

However in some of .NET Framework 4.7.2 SDK-style tests projects that wasn't enough.

The issue was with PlatformTarget project property. If unspecified it defaults to AnyCPU, however NUnit seems to always fail with

No test is available in Foo.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.

if it was left unspecified.

So, besides the PackageReference, I had to either:

Just set <PlatformTarget>x86</PlatformTarget>.
Explicitly set <PlatformTarget>AnyCPU</PlatformTarget> (even though it is AnyCPU if unspecified) and then in Test tab set "Processor Architecture for AnyCPU Projects" to "x86".

score 0 · Answer 33 · answered Jan 28 '19 at 17:10

In my case Reinstalling Nunit3 Adapter, Deleting temp folders, Changing architecture and nothing worked. Its because of the Daemon Resharper caused the problem.

Add or Remove Programs> Find Resharper > Repair > Install again > Restart VS

That resolves the issues.

score 0 · Answer 34 · edited May 08 '19 at 06:09

0

After add the TestAdapterPath in the commander, it's worked for me:

vstest.console.exe Xom.Gci.Lvf.FileParserInvoker.UnitTests.dll /TestAdapterPath:"C:\****\****\{SolutionFolder}"

edited May 08 '19 at 06:09

tryingToLearn

10,691
12
80
114

answered May 08 '19 at 05:59

dixiashi

1

First things, you should make sure that the test case can be run in the VS IDE. – dixiashi May 08 '19 at 06:00

Falco Alexander · Answer 35 · 2019-05-20T13:40:46.593

In my case the tests were discovered but running resulted in "Test not Available..." and the (in)famous: "Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again."

the error was independent of Visual Studio (tested from dotnet CLI tools and nearly naked UNit test) and it was only when targeting .NET 4.7.1. dotnetcore app works fine.

also running tests with the Nuint3 CLI nunit3-console.exe Tests.csproj shows the error:

"Either assembly contains no tests or proper test driver has not been found."

the error was because the test-adapter could not be found on a (mapped) network drive or share and was solved by copy it locally and rerun.

score 0 · Answer 36 · answered Jan 11 '23 at 15:21

0

For me the problem was an old reference to Microsoft.VisualStudio.TestPlatform. You don't need an explicit reference to this package because MSTest.TestFramework has a transitive reference to this package with a correct version.

answered Jan 11 '23 at 15:21

Artur

4,595
25
38

score 0 · Answer 37 · answered Jan 16 '23 at 12:59

One more random thing to do is to add the file xunit.runner.json.

Example configuration:

{
  "$schema": "https://xunit.net/schema/current/xunit.runner.schema.json",
  "appDomain": "ifAvailable",
  "shadowCopy": false,
  "parallelizeTestCollections": false,
  "maxParallelThreads": 1
}

Don't forget to include it in the project:

<ItemGroup>
  <Content Include="xunit.runner.json" CopyToOutputDirectory="PreserveNewest" />
</ItemGroup>

In my case, this was the magical remedy.

score 0 · Answer 38 · answered Jan 22 '23 at 17:22

If your solution only has one test file, check it has the .cs file extension.

I used the dotnet command to create a new test project for myself. I hastily renamed the generated class (UnitTest1.cs) without the .cs file extension.

This is similar to @Jared-Beach's scenario: obviously no tests were found via the IDE nor the command line. Beyond the first three words, the rest of the error message will point you in the wrong direction.

score 0 · Answer 39 · answered Jul 11 '23 at 08:05

0

I got this error because I had accidentally changed the Tests.cs file Compile action to 'None'.

answered Jul 11 '23 at 08:05

Rye bread

1,305
2
13
36

No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again

39 Answers39

Linked