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

[kieranbenton]

Reproduction at: https://github.com/kieranbenton/MyFirstUnitTests

Steps:

• 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

[bradwilson]

I believe this is a VS Code issue and should be opened there.

[kieranbenton]

Okay, I can do that. Have you got any further context as to why its likely with them and not V3?

…

On Tue, 31 Dec 2024, 17:23 Brad Wilson, ***@***.***> wrote: I believe this is a VS Code issue and should be opened there. — Reply to this email directly, view it on GitHub <#433 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJRMUCUNAMDMMBGOOGURD2ILHH7AVCNFSM6AAAAABUJ6RZ7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGYYDQNJSGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bradwilson]

Sorry, I have no insight into how the test explorer functionality in VS Code works, but the fact that the tests are detected and runnable and it's only the Code Lens functionality that disappears, should be enough of a starting place for them, I hope.

[kieranbenton]

Hi @bradwilson, the vscode guys have closed the bug I opened I'm afraid - they seem to have given some insight as to where the issue is in the extension though?

microsoft/vscode#237197 (comment)

[bradwilson]

I'll see what I can do.

[bradwilson]

I just responded on your other issue, but I can't reopen it. You'll have to do that.

[bradwilson]

Can you please try to reproduce the issue with 3.0.1-pre.7? https://xunit.net/docs/using-ci-builds

[bradwilson]

Because I'm not sure whether I've fixed it and just misunderstood what the issue is, or what. 😂

[bradwilson]

I will also try on macOS, see if it's OS environmental.

[bradwilson]

I do actually think this is fixed now. And I feel pretty dumb asking why they thought the fixed thing was broken. 😂

[kieranbenton]

Tested with the pre-release - sorted! Thanks @bradwilson !