Testing panel/tree broken

[pblivingston]

Describe the Issue

I have an xUnit (3.2.2) unit test project containing two tests that should fail and multiple theories with skipped tests. When running tests with dotnet test, the results appear as expected. When rolled back to C# Dev Kit extension version 3.10.14, the UI and results appear as expected.

When using the "Testing" panel/tree and its UI buttons in version 3.20.199:

• The "Refresh Tests" button and "Test: Refresh Tests" command are both missing.
• New tests are discovered on build, but old tests aren't removed from the tree/list and are marked "skipped" when tests are run
• Serialized theory data (IXunitSerializable) are not grouped by theory in the tree
• Theory data that should be skipped output "⚠️ ERROR: ExampleTest() - Test could not be run." in "Test Results", are marked as "errored" in the tree, and are reported as "skipped" in the Test Run Summary in "Test Results".
• The two tests that should fail are marked "skipped" and reported as "skipped" in the Test Run Summary.

Seems similar and may be related to #3188

Steps To Reproduce

Run skipped or failing xUnit tests using version 3.20.199 of the C# Dev Kit.

Expected Behavior

The testing panel should function properly - refresh button should not be missing, theory data should be grouped, and tests should report proper results.

Environment Information

• OS Version: Windows 11 25H2
• VS Code Version: 1.123.1
• Extension Version: 3.20.199

[CunesPoort8]

I have exactly the same problem, with the note that tests marked with '[Fact(Explicit = true)]' run good, but tests that use 'Assert.SkipWhen(condition, reason)' not. They get the 'Test could not be run.' message and appear errored in the tree.

Environment Information

OS Version: macOS Tahoe 26.5.1 (25F80)
VS Code Version: 1.123.0
Extension Version: 3.20.199

[KamilDabkowski]

Testing in new version is terrible,
no refresh button - on big changes need to restart IDE to find them
run all not necessary run all tests
testcases not grouped by test - this generate big mess
(switched back to 3.10.14 🤷‍♂️)

[lucas-pollus]

+1

[kjjablonowski-bp]

I'm also experiencing issues:

Observed Behavior

• Deleted test projects appearing in test tree
• Clicking "Run Tests" fails on the dotnet build step due to deleted test project names included in the /target list
  • Error: The target "<deleted_project_name>" does not exist in the project.

Impact

• Cannot run tests at all through the Testing pane

Attempted Fixes

• Cleared cache files for VS Code and the extension
• Reviewed .sln file to confirm deleted projects were removed
• Switched to extension version 3.10.14 (as others have said, this worked)

Environment

Test Framework: xUnit 3.2.2, MTP v2
OS Version: Windows 11 Enterprise 25H2
VS Code Version: 1.123.0
Extension Version: 3.20.199

[Kawodeda]

+1

[kakins]

I think ti's safe to say this latest update of the C# dev kit has been a pretty poor experience for many, myself included. I've found zero benefit but only drawbacks so far. One being the confusing nature of the new "consolidated" explorer view and now I can't refresh my tests.

[mistymeowmeow]

I am also seeing this. My workflow for adding new tests is pretty broken at the moment. Is this an intended change?

These testing issues, as well as the new solution explorer changes (not being able to add new files types in folders via solution explorer) has forced me to downgrade.

[tormodfj]

Our TDD workflows are essentially broken in 3.20.*. Had we just recently transitioned from VS 2026 to VS Code/C# Dev Kit, this would have been show-stopping friction, likely throwing is into the hands of JetBrains Rider.

Luckily, we've been using C# Dev Kit for a while, knowing that this worked in previous versions. Hence, downgrading to 3.10.* was the obvious workaround.

Nevertheless, it's sad to see regressions like this remaining unfixed for so long...