microsoft / microsoft/vscode-dotnettools

Test explorer can't navigate to test with errors

Open
#2,277 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-test bug
Dominant language
No language data
Stars
321
Forks
54
Avg merge
2d 19h
Merged PRs (30d)
2

Description

Describe the Issue

In a specific workspace. The test explorer doesn't work properly.

The Test Explorer works well when discovering and running tests, but when a test run encounters an error, the error icon is displayed on the test tab in VS Code. However, when I click on it, VS Code neither opens the test file nor displays the error.

The button to run a specific test near the line number does not appear either.

This error only occurs in one workspace. This problem doesn't occur in other workspaces. Can someone help me? Do I need to provide more information?

Steps To Reproduce

No response

Expected Behavior

No response

Environment Information

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure in the affected workspace through the VS Code Test Explorer, then compare it with a workspace where discovery and navigation work. Gather the missing reproduction and environment details, and consider the issue done when selecting an errored test opens its file and error and the line-level run button appears.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.