XUnit v3 packages cause VSCode 'codelens' debugging to become unavailable (tests are otherwise discovered okay in the sidebar)

[kieranbenton]

• VS Code Version: 1.96.2 (Universal)
• OS Version: Mac OS 15.1.1 (24B91)

Already opened as a bug on xunit but they think this is a VSCode issue: xunit/visualstudio.xunit#433.

Reproduction at: https://github.com/kieranbenton/MyFirstUnitTests ready to go.

Steps to Reproduce:

(NOTE: These are from scratch, but you can use the reproduction above to skip to the end).

• Follow the https://xunit.net/docs/getting-started/v2/netcore/cmdline tutorial

• Confirm that the minimal fact created as part of that is discoverable in the VSCode 'Testing' panel AND that the code lens actions are available for it

• Follow the v2 -> v3 migration steps (leaving the old package references commented out in csproj)

• dotnet clean, dotnet build - test is still discoverable in 'Testing' panel but the code lens actions AREN'T available

• Swap the package references back, dotnet clean + dotnet build - and its trivial to get the codelens support back

Nothing particularly smoking-gun esque in logs that I can find:

Tests removed: /Users/kieranbenton/Source/kaizenticketing/MyFirstUnitTests/bin/Debug/net9.0/MyFirstUnitTests.dll
Tests are available, running test discovery: /Users/kieranbenton/Source/kaizenticketing/MyFirstUnitTests/bin/Debug/net9.0/MyFirstUnitTests.dll
Scheduling discovery: /Users/kieranbenton/Source/kaizenticketing/MyFirstUnitTests/bin/Debug/net9.0/MyFirstUnitTests.dll [1735404920350]
========== Starting test discovery ==========
[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v3.0.0+e341b939fe (64-bit .NET 9.0.0)
[xUnit.net 00:00:00.26]   Discovering: MyFirstUnitTests
[xUnit.net 00:00:00.37]   Discovered:  MyFirstUnitTests
========== Test discovery finished: 1 Tests found in 590 ms ==========
1 tests discovered from /Users/kieranbenton/Source/kaizenticketing/MyFirstUnitTests/bin/Debug/net9.0/MyFirstUnitTests.dll in 590.0289 ms

[connor4312]

This would indicate that the debug extension is not associating a location (file or range) with the tests. Just doing a quick search on their extension it seems like other users might have this problem too, e.g. microsoft/vscode-dotnettools#1704

[vs-code-engineering]

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.

Happy Coding!

[bradwilson]

I disagree with the analysis that "we're not providing source information", because something is allowing a user to navigate from the test window to source code correctly (and that something is the source & line number metadata that is claimed isn't present).

The below video was captured using xunit.runner.visualstudio version 3.0.1-pre.7:

Recording.2025-01-06.105057.mp4

Can you please explain to me why navigation from the test tree into the source code works, but the icons don't, in a way that is our fault?

[kieranbenton]

@connor4312 can you reopen please and review @bradwilson 's information? Thanks.

[connor4312]

You case looks different from the reporter's. The reporter said that navigation stops working and the "run" buttons disappear, which is behavior consistent with a missing test location (their 3rd screenshot). In your case it seems like navigation works and the run buttons do appear correctly -- I don't see any issues with your recording.

[bradwilson]

Sorry, I may have simultaneously fixed the issue and misunderstood how it surfaced. 😬 😂

[connor4312]

All good, let me know if you run into anything else that might be vscode side :)