Vstest: Request to merge dotnet test and dotnet vstest into single command

Created on 28 Feb 2018 · 3Comments · Source: microsoft/vstest

Currently there are two different ways to run tests through dotnet cli:
$ dotnet test
$ dotnet vstest

According to @Faizan2304 in #637, these are both wrappers for the vstest.console.dll already and should be no real behavior differences between them. (source) As a CI/CD scripter, I want the ability to run tests with the dotnet cli without having to remember the distinction between the two, so that I can go faster and focus on more important details.

My acceptance criteria would be along the lines of:

The "dotnet test" command can be used in place of the "dotnet vstest" command.
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.

Stretch goals:

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.

Background:
I am looking into implementing new portions of my organization's CI/CD pipeline for our .NET Core applications. Some of those activities involve running unit and integration tests. I would like the ability to pass in the filename of either a .csproj or a .dll without having to change any other syntax of the dotnet test command.

enhancement

Source