formulahendry / vscode-dotnet-test-explorer

.NET Core Test Explorer for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=formulahendry.dotnet-test-explorer
MIT License
203 stars 96 forks source link

No tests shown in tree #39

Closed OliverCole closed 6 years ago

OliverCole commented 6 years ago

I have set dotnet-test-explorer.testProjectPath. The test explorer window still says

Please open or set the test project and ensure your project compiles.

The project compiles, the Run All Tests button works (and discovers tests), and the output file is written to the specificd path. The Refresh button doesn't seem to do anything.

mmcintyre123 commented 6 years ago

I have the exact same problem. I have the dotnet-test-explorer.testProjectPath set to the folder containing my csproj file and the Features folder which contains the tests.

teamdynamiq commented 6 years ago

Hmm, could you try to just open the test project folder directly (so that the testProjectPath is not needed) and give that a spin?.

(On a side note maybe it would be helpful to add a setting to the extension for writing some form of debug log file with internal errors.)

AOne-T commented 6 years ago

Same issue. "Run all tests" button tries to run as tests all projects in my workfolder (solution). Also in my case I need a way to set the SolutionDir environment variable before building/running tests.

TFTomSun commented 6 years ago

I have the same issue. I try to run NUnit tests under Windows 7. .NET Core SDK 2.1.3 is installed. When i refresh the test explorer the following message is shown:

Testlauf f�r "D:\Git\Tooling\src\Siemens.MindSphere.Nfr.Tests\bin\Debug\netcoreapp2.1\Siemens.MindSphere.Nfr.Tests.dll" (.NETCoreApp,Version=v2.1)
Microsoft (R) Testausf�hrungs-Befehlszeilentool Version 15.7.0
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

Die folgenden Tests sind verf�gbar:
    FirstContactNfrTest
    OpenFlowCreatorTest
    FirstContactNfrTest
    OpenFlowCreatorTest
    FirstContactNfrTest
    OpenFlowCreatorTest
    FirstContactNfrTest
    OpenFlowCreatorTest

    at executeDotnetTest.then (C:\Users\adfrth5\.vscode\extensions\formulahendry.dotnet-test-explorer-0.4.0\out\src\testDiscovery.js:17:19)
    at <anonymous>:null:null

So the tests are actually discovered, but then this error happens.

Now I got this output:


Executing dotnet test -t -v=q in D:\Git\Tooling\src\Siemens.MindSphere.Nfr.Tests
[ERROR] Error while executing dotnet test -t -v=q - Error: Command failed: dotnet test -t -v=q

    at ChildProcess.exithandler (child_process.js:217:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:194:7)
    at maybeClose (internal/child_process.js:899:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

[ERROR] Error while discovering tests - Error: Command failed: dotnet test -t -v=q

    at ChildProcess.exithandler (child_process.js:217:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:194:7)
    at maybeClose (internal/child_process.js:899:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
stefanforsberg commented 6 years ago

@TFTomSun This is probably related to running dotnet tooling in a non english language, have a look at #77 for a "solution"

TFTomSun commented 6 years ago

@stefanforsberg Thanks for the hint. The workaround solved the issue for me.

For everybody who come across this thread:

bmccord commented 5 years ago

I just found the cause for it happening on my machine. I had a "Path For Result File" set, but the specified folder didn't exist on one of my projects. That caused the "Discovering Tests" to just spin forever. I took out the Path, restarted, and tests were found quickly.

AboubakarAhamada commented 4 years ago

@stefanforsberg Thanks for the hint. The workaround solved the issue for me.

For everybody who come across this thread:

  • Go to C:\Program Files\dotnet\sdk
  • move all language folders (e.g. cs, de, en, es, ... zh-*) to a subfolder
  • Start Visual Studio code
  • Refresh the test explorer -> the tests are shown now

After two weeks stucking on this issue, this finaly worked for me. Thanks

dotnetdew commented 2 years ago

@stefanforsberg Thanks for the hint. The workaround solved the issue for me. For everybody who come across this thread:

  • Go to C:\Program Files\dotnet\sdk
  • move all language folders (e.g. cs, de, en, es, ... zh-*) to a subfolder
  • Start Visual Studio code
  • Refresh the test explorer -> the tests are shown now

After two weeks stucking on this issue, this finaly worked for me. Thanks

that is not worked