-
Notifications
You must be signed in to change notification settings - Fork 97
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
Running induvidual tests doesn't work - Could not find a matching test directory for test #355
Comments
I am having the same problem trying to run an individual test from this Test Explorer. I am also not able to run a test by clicking the "Debug Test" link shown in the source code. I am able to run a test by typing |
I'm encountering a very similar issue, but when running individual tests it fails finding things during build rather than run. It seems to randomly come and go.
|
I have the same issue, running any individual test gives me an issue like this:
The file is located under |
I am also having the same issue (with XUnit), trying to use the unit test explorer capability with QSharp applications. I can use the extension to run all tests, but individual ones do not work. Upon running all tests: Upon running an individual one: |
Hello,
I have Unity project with NUnit tests. If I open Testing tab, there are not tests visible:
console output:
Starting extension Finding projects for pattern /home/pavel/NetBeansProjects/imperium/Assets/Tests/*/Tests.*.csproj Found 2 matches for pattern in folder /home/pavel/NetBeansProjects/imperium Evaluating match /home/pavel/NetBeansProjects/imperium/Assets/Tests/core/Tests.Core.csproj Adding directory /home/pavel/NetBeansProjects/imperium/Assets/Tests/core Evaluating match /home/pavel/NetBeansProjects/imperium/Assets/Tests/def/Tests.Def.csproj Adding directory /home/pavel/NetBeansProjects/imperium/Assets/Tests/def Executing dotnet test -t -v=q in /home/pavel/NetBeansProjects/imperium/Assets/Tests/core
If I click run all button, all tests runs just fine:
console output:
`
Executing dotnet build in /home/pavel/NetBeansProjects/imperium/Assets/Tests/core
Executing dotnet test --no-build --logger "trx;LogFileName=/tmp/test-explorer-apqaEd/0.trx" in /home/pavel/NetBeansProjects/imperium/Assets/Tests/core
Process 11783 started
Test run for /home/pavel/NetBeansProjects/imperium/Temp/tests.core/Bin/Debug/net6.0/tests.core.dll (.NETCoreApp,Version=v6.0)
Microsoft (R) Test Execution Command Line Tool Version 17.1.0
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
Results File: /tmp/test-explorer-apqaEd/0.trx
Passed! - Failed: 0, Passed: 12, Skipped: 0, Total: 12, Duration: 727 ms - /home/pavel/NetBeansProjects/imperium/Temp/tests.core/Bin/Debug/net6.0/tests.core.dll (net6.0)
Process 11783 finished
Executing dotnet build in /home/pavel/NetBeansProjects/imperium/Assets/Tests/def
Executing dotnet test --no-build --logger "trx;LogFileName=/tmp/test-explorer-apqaEd/1.trx" in /home/pavel/NetBeansProjects/imperium/Assets/Tests/def
Process 11882 started
Test run for /home/pavel/NetBeansProjects/imperium/Temp/tests.def/Bin/Debug/net6.0/tests.def.dll (.NETCoreApp,Version=v6.0)
Microsoft (R) Test Execution Command Line Tool Version 17.1.0
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
Results File: /tmp/test-explorer-apqaEd/1.trx
Passed! - Failed: 0, Passed: 30, Skipped: 0, Total: 30, Duration: 354 ms - /home/pavel/NetBeansProjects/imperium/Temp/tests.def/Bin/Debug/net6.0/tests.def.dll (net6.0)
Process 11882 finished
`
If I run individuals test or test group, I will get error:
[WARNING] Could not find a matching test directory for test imperium.tests.core.ConfigLoaderTest
I've tried to find more info what does this mean. How and where I can set "matching" test directory. But I've found nothing.
I don't know if problem is in project settings, VSCode settings, test explorer settings, vsocde bug, test explorer bug, dotnet bug or something else.
The text was updated successfully, but these errors were encountered: