We use NUnit for our unit tests. Locally, it works fine and expected. I conclude that the NUnit3TestAdapter is there and found.
But on CI, when the same exact dotnet test command is called, it's not running the NUnit runner but VSTest. CI has the same environment as my local machine, down to the SDK version. Same OS (Linux), no significantly different environment variables. NUnit3TestAdapter is also where it belongs.
Appending -v diagnostic gives me a huge log, but it also seems to now work with the NUnit runner, as it does locally. I have not found another parameter that changes the behaviour.
My best guess is that there is some race condition where it can't find the NUnit runner quickly enough. But that is only a guess and I'd be happy for fixes.
We use NUnit for our unit tests. Locally, it works fine and expected. I conclude that the NUnit3TestAdapter is there and found.
But on CI, when the same exact
dotnet testcommand is called, it's not running the NUnit runner but VSTest. CI has the same environment as my local machine, down to the SDK version. Same OS (Linux), no significantly different environment variables.NUnit3TestAdapteris also where it belongs.Appending
-v diagnosticgives me a huge log, but it also seems to now work with the NUnit runner, as it does locally. I have not found another parameter that changes the behaviour.My best guess is that there is some race condition where it can't find the NUnit runner quickly enough. But that is only a guess and I'd be happy for fixes.