Skip to content
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

Test Explorer is empty and 'No tests found in the selected file or folder' for Run/Debug Tests context menu #234102

Closed
kosa-gyula-77 opened this issue Nov 18, 2024 · 2 comments
Assignees
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@kosa-gyula-77
Copy link

kosa-gyula-77 commented Nov 18, 2024

C# test project references

  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <IsTestProject>true</IsTestProject>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.5.0" />
    <PackageReference Include="NUnit" Version="3.13.3" />
    <PackageReference Include="NUnit3TestAdapter" Version="4.4.2" />
    <PackageReference Include="NUnit.Analyzers" Version="3.6.1" />
    <PackageReference Include="coverlet.collector" Version="3.2.0" />
  </ItemGroup>

Visual Studio Code

Version: 1.95.3 (user setup)
Commit: f1a4fb1
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

C# Dev Kit

v1.13.9

Symptoms

  1. Test Explorer is empty. It renders 'No tests have been found in the worskpace yet.'
  2. 'No tests found in the selected file or folder' is rendered when selecting Run Tests/Debug Tests context menu on a test class file or test project.
@connor4312 connor4312 added the *caused-by-extension Issue identified to be caused by an extension label Nov 18, 2024
Copy link

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!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 18, 2024
@kosa-gyula-77
Copy link
Author

Reported at microsoft/vscode-dotnettools#1620

@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Jan 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

2 participants