formulahendry / formulahendry/vscode-dotnet-test-explorer

Discovering Tests process does NOT populate the .NET Test Explorer Pane

Open
#346 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
208
Forks
93
PR merge metrics
No merged PRs in 30d

Description

Project Path issue...

I've read too many posts about this issue and can't find a solution for the discovery process to work...
But, still, on the .Net Test Explorer (v0.7.7) Pane on VSCode Version: 1.62.3 (user setup), the tests can only be found if I click on the "Run All Tests" button, (which is not what I need.) and it keeps giving me the "No tests found", even after tests are discovered by clicking on "Run All Tests" I can't run a specific test...

When I open VSCode and look at the .Net Test Explorer output, it reads like this:
Starting extension
Finding projects for pattern c:/[path to my project]/**/*.Tests.csproj
Found 1 matches for pattern in folder c:\[path to my project]
Evaluating match c:/[path to my project]/XYX.Tests/XYZ.Tests.csproj
Adding directory c:/[path to my project]/XYZ.Tests
Executing dotnet test -t -v=q in c:/[path to my project]/XYZ.Tests

Manually executing the command "dotnet test -t -v=n [full test project path]" it tells me that all X tests were found...

These are the package references on my main/test .csproj files...
Microsoft.NET.Test.Sdk - Version=17.0.0
NUnit - Version=3.13.2
NUnit.Console - Version=3.11.1
NUnit3Testadapter - Version=4.1.0
TestCentric.Metadata - Version=1.7.1

Sorry if I missed the post that fixes this issue... can someone give me some other places to look?
IDK what else can be looked at :(

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.