CharliePoole

@jnm2 @mikkelbu Any thoughts on this?

I'm fleshing this out further and starting to work on it. Hoping that it will make enough sense to engender comments as I get more into the details! Here's how...

The workaround we have used in the past is to provide a unique name to the TestAgency when it is created. However, this is only possible if your test is...

Here's code where we test TestAgency itself. We construct it so that the URL includes "TestAgencyTest" rather than just "TestAgency". https://github.com/nunit/nunit-console/blob/4a1820c4fcec38329ecb4473ccd244d6572d91a5/src/NUnitEngine/nunit.engine.tests/Services/TestAgencyTests.cs#L21 However, you want this engine to be injected in...

@Kuling The console runner makes no use whatsoever of the runtimeconfig file. Only the runner used by the dotnet command does that.

No, I'm not saying that you can't run your tests - although obviously there's an issue to solve. I'm just taking note of the side issue, which is that you...

I'm using @Kuling 's workaround as the base of the solution, modifying the project file so that the `nunit-agent.runtimeconfig.json` is generated that way. I'll add tests to ensure it keeps...

I think that the fix will also resolve #1202, but I have kept that open pending confirmation.

@cw397 Thanks for checking!

This issue has been resolved in version 3.16.0 The release is available on: [GitHub](https://github.com/nunit/nunit-console/releases/tag/3.16.0). NuGet packages are also available [NuGet.org](https://www.nuget.org) and Chocolatey Packages may be found at [Chocolatey.org](https://chocolatey.org)