1

I am using Visual Studio 2019 and latest Resharper. I have Nunit3 installed along with test adapters. I keep on getting this error. Can someone help me on this

[1]: https://i.stack.imgur.com/qbcPH.png

SandyRocks
  • 269
  • 4
  • 15
  • We do not have enough information to answer your question. Please [edit] your question to include enough information for a [repro]. Offhand, the test is neither failing, nor passing. it is inconclusive just like the test results say. Please post the gherkin scenario and the step definitions. – Greg Burghardt Jan 10 '23 at 14:12
  • I solved it by removing all bins and recompiling all from MSBuild command line outside VS, then restarting VS – Patrick from NDepend team Feb 02 '23 at 06:53

5 Answers5

1

I got the problem. If your test projects are using the SDK project style.

You should add this code into your csprj file.

  <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>     <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>

If your test project app.config file:

  1. The app.config contains only binding redirects, you can delete the entire file
  2. The app.config contains setting, you should delete the binding redirects parts
hoangsnowy
  • 256
  • 1
  • 4
0

Check you App.config file - maybe some dependencies are corrupted.

I just had the same issue, and it turned out that the runtime section in App.config had two nested assemblyBinding tags. I fixed that, and the error disappeared.

taisalonga
  • 1
  • 2
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jan 17 '23 at 13:24
0

I got this error when I was using an old Version of FakeItEasy(3.3.2) or RhinoMock together with Nunit3. Upgrading to a recent version solved that error for me.

Bluescreenterror
  • 106
  • 9
0

In my case, it's because the test assembly has the same exact name as the assembly under test.

I scaled down my test assembly to only 1 test case, and then a different error appeared-- cannot load from type exception. That pointed me in the correct direction.

Graviton
  • 81,782
  • 146
  • 424
  • 602
0

All the answers above are valuable, however in my case there was [TestFixture] attribute in some base class, which don't had any tests inside. Removing this redundant attribute helped to solve the "inconclusive" issue.

vts123
  • 1,736
  • 6
  • 27
  • 41