-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Dotnet CLI #1402
Comments
This is currently a limitation of the Microsoft testing platform and not possible yet |
Do you know of any other way I could do discovery and get all the information from each test? |
What's your use case? All your tests are available in an After(TestDiscovery) hook - You can interrogate all the information of them there. |
Rider did not discorver all my tests. This command |
I'm creating a vscode extension... so I would like to discover all the tests... |
Enable Testing Platform support, https://thomhurst.github.io/TUnit/docs/tutorial-basics/running-your-tests |
Might wanna upvote this issue: microsoft/testfx#3221 |
Thanks, but it's already enabled. It works for other tests in the same project. But it doesnt discover new tests for a while. I've restarted rider a couple times, now it discovered them fine. Really annoying. Had the same problem with the first tests as well ** edit: Totally my bad.. I didnt realise rider was showing me a subset of the test, sort of like a profile or a playlist like in VS. All tests show up without problem in the 'explorer' tab. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I would like to discover all the tests, using the command below it returns all the tests, but only the names... how to get the qualified name type namespace/class/name
dotnet run --project .\mytests.csproj --list-tests
The text was updated successfully, but these errors were encountered: