CODEWITHSUNDEEP
c#nunit
Julien N
Julien N

Reputation: 3920

NUnit TestEngine throws "Unable to load one or more of the requested types" when trying to explore assembly

I'm working on a tool that needs to extract the NUnit tests names that are contained in an assembly.
As I need the exact name of the tests when they are run, and NUnit's way of naming the tests is not straightforward, I use the NUnit TestEngine to explore the assembly.

Something like that :

    Assembly testAssembly; //loaded somewhere else

    using var testEngine = new TestEngine();
    testEngine.WorkDirectory = Path.GetDirectoryName(testAssembly.Location);
    var       package    = new TestPackage(testAssembly.Location);
    using var runner     = testEngine.GetRunner(package);
    var       testsFound = runner.Explore(new TestFilter(string.Empty));

I build the whole tool with one of our projects as test subject, and it works well. But when I try it on other similar projects (.Net 6, NUnit test projects for a web API), I have the following error :

Unable to load one or more of the requested types.
Could not load file or assembly 'Microsoft.AspNetCore.Hosting.Abstractions, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.

The tests run properly inside the Visual Studio, with VS test runner or Resharper.
The current directory is set to the bin folder.

Looking at the project, it seems that this is a implicit dependency of Microsoft.AspnetCore.Hosting (referenced by AppInsight)

dependencies

But :

I can't find where this reference is needed and why one solution is working and others are not, while they are very similar !

I'm out of ideas to make it work, so I'm looking for suggestions.

Upvotes: 0

Views: 370

Answers (1)

Charlie
Charlie

Reputation: 13736

Have you considered simply telling NUnit to produce the list of tests for you?

The --explore option followed by a file name creates XML output but without a following name it produces a readable list of names on the console. You can redirect the output to a file if that's what you want.

nunit3-console yourtests.dll --explore

UPDATE

Make sure you use the standard .NET Framework build of NUnit3-console with the above option, not the .NET 6.0 build. The standard runner creates whatever process is needed to properly explore the test assembly.

Upvotes: 1

Related Questions