Problem if OutputXmlFolderMode setting is not in .runsettings

[varnk]

• NUnit 3.13.1
• NUnit3TestAdapter 4.3.0
• Visual Studio 2022 Enterprise Version 17.4.0
• .NET Framework 4.6.1

When I have a .runsettings file selected in VS with a missing OutputXmlFolderMode setting, I cannot run or debug any tests. Visual Studio starts the test for a short time, and then the debug session just ends without any message or without hitting any of the code in the test. Once I added the OutputXmlFolderMode into the .runsettings file, the test started working again.

local.runsettings file attached with OutputXmlFolderMode set. Remove the OutputXmlFolderMode line to reproduce the problem.

local.zip

[OsirisTerje]

@varnk That's correct. It is fixed in the 4.3.1, ETA 1-2 days or so. See #1026 and #1027. There is an alpha there too, if you want to try.

I'll still mark this as a bug, since it is not explicitly set earlier, just as a comment within the two above.

[varnk]

Looks like this problem also exists in Visual Studio 2022 Version 17.4.0 with the NUnit3TestAdapter 4.2.1. I don't believe this version of the TestAdapter supports the OutputXmlFolderMode, so maybe this is a different issue.

[OsirisTerje]

That might be true. But if you run under netcore it should work. Have you checked the alpha version?

[OsirisTerje]

Released here https://www.nuget.org/packages/NUnit3TestAdapter/4.3.1

[netcorefactory]

we should not presume everyone is on net.core?

[OsirisTerje]

@netcorefactory No :-)