Skip to content

vstest.console fails to connect when using any NUnit version below 4 #3231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Hertzole opened this issue Apr 23, 2025 · 2 comments
Open

vstest.console fails to connect when using any NUnit version below 4 #3231

Hertzole opened this issue Apr 23, 2025 · 2 comments
Labels
🐛 Bug Something isn't working

Comments

@Hertzole
Copy link

Describe the bug
I try to run stryker on my project and it always failed when trying to connect to the vstest.console. Currently my project is using NUnit 3.14.0 (woo, I just love supporting unity...) and then it fails. However, if I upgrade just a step to NUnit 4.0.1, it works just fine. But I can't use 4.0.1 because my library needs to test against older .NET versions.

Logs

log-20250423.txt

Expected behavior
I expect stryker to run without issues even if I'm using NUnit 3.14.0.

Desktop (please complete the following information):

  • OS: Linux (Manjaro Arch)
  • Type of project: Core
  • Framework Version: .NET Standard 2.0, .NET Standard 2.1, .NETCoreApp3.1, .NET 5, .NET 6, .NET 8
  • Stryker Version 4.5.1

Additional context
These are the (what I think is) relevant packages I have installed for testing.

<PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.1.0"/>
<PackageReference Include="NUnit" Version="3.14.0" />
<PackageReference Include="NUnit3TestAdapter" Version="5.0.0"/>
<PackageReference Include="NUnit.Analyzers" Version="3.3.0"/>
@Hertzole Hertzole added the 🐛 Bug Something isn't working label Apr 23, 2025
@dupdob
Copy link
Member

dupdob commented Apr 24, 2025

Hello
Could you please try running VsTest on your test project from the CLI and see what happens ?

This error js a hint that VsTest fails during initialization. Stryker cannot get any more details than this.

@Hertzole
Copy link
Author

Running dotnet vstest on my built dll files works just fine, as well as just running dotnet test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants