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

Docs on dotnet test arguments coming from vstest are missing #41773

Open
dhrumil0902 opened this issue Jul 16, 2024 · 0 comments
Open

Docs on dotnet test arguments coming from vstest are missing #41773

dhrumil0902 opened this issue Jul 16, 2024 · 0 comments
Labels
doc-idea Indicates issues that are suggestions for new topics [org][type][category] Pri3 ⌚ Not Triaged Not triaged

Comments

@dhrumil0902
Copy link

Proposed topic or title

Vstest Arguments Transferred to DotNet Test

Location in table of contents.

No response

Reason for the article

According to the dotnet vstest documentation page, the command is superseded by the dotnet test command, which can now be used to run assemblies.

Which, I believe, was done as a result of microsoft/vstest#1453 request in a scope of microsoft/vstest-docs#196.

dotnet vstest is able to run tests from the assemblies in parallel if --parallel flag is provided. Per the referenced microsoft/vstest-docs#196, there was an intention to support the same behavior for the dotnet test command as well.

Success criteria (as per user ask)

The "dotnet test" command can be used in place of the "dotnet vstest" command.
The "dotnet test" command can accept a list of dlls
Using "dotnet test" and targeting a list of dlls, there is an argument for "--parallel" which will run the tests from the dlls in parallel.
Using "dotnet test" and targeting a dll, the inclusion or exclusion of the "--no-build" argument will have no impact on the behavior of execution.
My local testing confirms that --parallel flag is respected and tests are run in parallel; test from the assemblies are run sequentially otherwise. Note, that I'm talking parallel execution of the assemblies themselves and not the internal assembly-level of tests parallelization, which is handled by NUnit and its adapter for me.

However, there is no documentation for that feature at the dotnet test page and in the output of the dotnet test --help command, which is confusing.

Is parallel execution of tests from assemblies supported by the dotnet test command officially, and it's safe to rely on that, or it's an implementation detail exposed accidentally?
Should the documentation for dotnet test be updated to reflect that?

Article abstract

More information about how exisiting features of vstest can be used in dotnet test.

Relevant searches

dotnet test --parallel
dotnet test
dotnet test and vstest integration

@dhrumil0902 dhrumil0902 added the doc-idea Indicates issues that are suggestions for new topics [org][type][category] label Jul 16, 2024
@dotnet-bot dotnet-bot added ⌚ Not Triaged Not triaged labels Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-idea Indicates issues that are suggestions for new topics [org][type][category] Pri3 ⌚ Not Triaged Not triaged
Projects
None yet
Development

No branches or pull requests

2 participants