Add dotnet-tool manpages and update others
This commit is contained in:
parent
de407deff0
commit
5f93685491
29 changed files with 1895 additions and 215 deletions
|
@ -1,5 +1,5 @@
|
|||
.\"t
|
||||
.\" Automatically generated by Pandoc 2.1.3
|
||||
.\" Automatically generated by Pandoc 2.2.1
|
||||
.\"
|
||||
.TH "dotnet test command \- .NET Core CLI" "1" "" "" ".NET Core"
|
||||
.hy
|
||||
|
@ -9,11 +9,21 @@
|
|||
.PP
|
||||
\f[C]dotnet\ test\f[] \- .NET test driver used to execute unit tests.
|
||||
.SH SYNOPSIS
|
||||
.SS .NET Core 2.x
|
||||
.SS .NET Core 2.1
|
||||
.IP
|
||||
.nf
|
||||
\f[C]
|
||||
dotnet\ test\ [<PROJECT>]\ [\-a|\-\-test\-adapter\-path]\ [\-c|\-\-configuration]\ [\-\-collect]\ [\-d|\-\-diag]\ [\-f|\-\-framework]\ [\-\-filter]\ [\-l|\-\-logger]\ [\-\-no\-build]\ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-results\-directory]\ [\-s|\-\-settings]\ [\-t|\-\-list\-tests]\ [\-v|\-\-verbosity]
|
||||
dotnet\ test\ [<PROJECT>]\ [\-a|\-\-test\-adapter\-path]\ [\-\-blame]\ [\-c|\-\-configuration]\ [\-\-collect]\ [\-d|\-\-diag]\ [\-f|\-\-framework]\ [\-\-filter]
|
||||
\ \ \ \ [\-l|\-\-logger]\ [\-\-no\-build]\ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-results\-directory]\ [\-s|\-\-settings]\ [\-t|\-\-list\-tests]\ [\-v|\-\-verbosity]
|
||||
dotnet\ test\ [\-h|\-\-help]
|
||||
\f[]
|
||||
.fi
|
||||
.SS .NET Core 2.0
|
||||
.IP
|
||||
.nf
|
||||
\f[C]
|
||||
dotnet\ test\ [<PROJECT>]\ [\-a|\-\-test\-adapter\-path]\ [\-c|\-\-configuration]\ [\-\-collect]\ [\-d|\-\-diag]\ [\-f|\-\-framework]\ [\-\-filter]
|
||||
\ \ \ \ [\-l|\-\-logger]\ [\-\-no\-build]\ [\-\-no\-restore]\ [\-o|\-\-output]\ [\-r|\-\-results\-directory]\ [\-s|\-\-settings]\ [\-t|\-\-list\-tests]\ [\-v|\-\-verbosity]
|
||||
dotnet\ test\ [\-h|\-\-help]
|
||||
\f[]
|
||||
.fi
|
||||
|
@ -41,10 +51,84 @@ Test projects specify the test runner using an ordinary \f[C]<PackageReference>\
|
|||
.PP
|
||||
\f[C]PROJECT\f[]
|
||||
.PP
|
||||
Specifies a path to the test project.
|
||||
If omitted, it defaults to current directory.
|
||||
Path to the test project.
|
||||
If not specified, it defaults to current directory.
|
||||
.SH OPTIONS
|
||||
.SS .NET Core 2.x
|
||||
.SS .NET Core 2.1
|
||||
.PP
|
||||
\f[C]\-a|\-\-test\-adapter\-path\ <PATH_TO_ADAPTER>\f[]
|
||||
.PP
|
||||
Use the custom test adapters from the specified path in the test run.
|
||||
.PP
|
||||
\f[C]\-\-blame\f[]
|
||||
.PP
|
||||
Runs the tests in blame mode.
|
||||
This option is helpful in isolating the problematic tests causing test host to crash.
|
||||
It creates an output file in the current directory as \f[I]Sequence.xml\f[] that captures the order of tests execution before the crash.
|
||||
.PP
|
||||
\f[C]\-c|\-\-configuration\ {Debug|Release}\f[]
|
||||
.PP
|
||||
Defines the build configuration.
|
||||
The default value is \f[C]Debug\f[], but your project's configuration could override this default SDK setting.
|
||||
.PP
|
||||
\f[C]\-\-collect\ <DATA_COLLECTOR_FRIENDLY_NAME>\f[]
|
||||
.PP
|
||||
Enables data collector for the test run.
|
||||
For more information, see Monitor and analyze test run.
|
||||
.PP
|
||||
\f[C]\-d|\-\-diag\ <PATH_TO_DIAGNOSTICS_FILE>\f[]
|
||||
.PP
|
||||
Enables diagnostic mode for the test platform and write diagnostic messages to the specified file.
|
||||
.PP
|
||||
\f[C]\-f|\-\-framework\ <FRAMEWORK>\f[]
|
||||
.PP
|
||||
Looks for test binaries for a specific framework.
|
||||
.PP
|
||||
\f[C]\-\-filter\ <EXPRESSION>\f[]
|
||||
.PP
|
||||
Filters out tests in the current project using the given expression.
|
||||
For more information, see the Filter option details section.
|
||||
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
|
||||
.PP
|
||||
\f[C]\-h|\-\-help\f[]
|
||||
.PP
|
||||
Prints out a short help for the command.
|
||||
.PP
|
||||
\f[C]\-l|\-\-logger\ <LoggerUri/FriendlyName>\f[]
|
||||
.PP
|
||||
Specifies a logger for test results.
|
||||
.PP
|
||||
\f[C]\-\-no\-build\f[]
|
||||
.PP
|
||||
Doesn't build the test project before running it.
|
||||
It also implicit sets the \f[C]\-\-no\-restore\f[] flag.
|
||||
.PP
|
||||
\f[C]\-\-no\-restore\f[]
|
||||
.PP
|
||||
Doesn't execute an implicit restore when running the command.
|
||||
.PP
|
||||
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
|
||||
.PP
|
||||
Directory in which to find the binaries to run.
|
||||
.PP
|
||||
\f[C]\-r|\-\-results\-directory\ <PATH>\f[]
|
||||
.PP
|
||||
The directory where the test results are going to be placed.
|
||||
If the specified directory doesn't exist, it's created.
|
||||
.PP
|
||||
\f[C]\-s|\-\-settings\ <SETTINGS_FILE>\f[]
|
||||
.PP
|
||||
Settings to use when running tests.
|
||||
.PP
|
||||
\f[C]\-t|\-\-list\-tests\f[]
|
||||
.PP
|
||||
List all of the discovered tests in the current project.
|
||||
.PP
|
||||
\f[C]\-v|\-\-verbosity\ <LEVEL>\f[]
|
||||
.PP
|
||||
Sets the verbosity level of the command.
|
||||
Allowed values are \f[C]q[uiet]\f[], \f[C]m[inimal]\f[], \f[C]n[ormal]\f[], \f[C]d[etailed]\f[], and \f[C]diag[nostic]\f[].
|
||||
.SS .NET Core 2.0
|
||||
.PP
|
||||
\f[C]\-a|\-\-test\-adapter\-path\ <PATH_TO_ADAPTER>\f[]
|
||||
.PP
|
||||
|
@ -72,7 +156,7 @@ Looks for test binaries for a specific framework.
|
|||
.PP
|
||||
Filters out tests in the current project using the given expression.
|
||||
For more information, see the Filter option details section.
|
||||
For additional information and examples on how to use selective unit test filtering, see Running selective unit tests.
|
||||
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
|
||||
.PP
|
||||
\f[C]\-h|\-\-help\f[]
|
||||
.PP
|
||||
|
@ -84,11 +168,12 @@ Specifies a logger for test results.
|
|||
.PP
|
||||
\f[C]\-\-no\-build\f[]
|
||||
.PP
|
||||
Does not build the test project prior to running it.
|
||||
Doesn't build the test project before running it.
|
||||
It also implicit sets the \f[C]\-\-no\-restore\f[] flag.
|
||||
.PP
|
||||
\f[C]\-\-no\-restore\f[]
|
||||
.PP
|
||||
Doesn't perform an implicit restore when running the command.
|
||||
Doesn't execute an implicit restore when running the command.
|
||||
.PP
|
||||
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
|
||||
.PP
|
||||
|
@ -97,7 +182,7 @@ Directory in which to find the binaries to run.
|
|||
\f[C]\-r|\-\-results\-directory\ <PATH>\f[]
|
||||
.PP
|
||||
The directory where the test results are going to be placed.
|
||||
The specified directory will be created if it doesn't exist.
|
||||
If the specified directory doesn't exist, it's created.
|
||||
.PP
|
||||
\f[C]\-s|\-\-settings\ <SETTINGS_FILE>\f[]
|
||||
.PP
|
||||
|
@ -134,7 +219,7 @@ Looks for test binaries for a specific framework.
|
|||
.PP
|
||||
Filters out tests in the current project using the given expression.
|
||||
For more information, see the Filter option details section.
|
||||
For additional information and examples on how to use selective unit test filtering, see Running selective unit tests.
|
||||
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
|
||||
.PP
|
||||
\f[C]\-h|\-\-help\f[]
|
||||
.PP
|
||||
|
@ -146,7 +231,7 @@ Specifies a logger for test results.
|
|||
.PP
|
||||
\f[C]\-\-no\-build\f[]
|
||||
.PP
|
||||
Does not build the test project prior to running it.
|
||||
Doesn't build the test project before running it.
|
||||
.PP
|
||||
\f[C]\-o|\-\-output\ <OUTPUT_DIRECTORY>\f[]
|
||||
.PP
|
||||
|
@ -186,7 +271,7 @@ The following are the properties supported by popular unit test frameworks:
|
|||
.PP
|
||||
.TS
|
||||
tab(@);
|
||||
c l.
|
||||
l l.
|
||||
T{
|
||||
Test Framework
|
||||
T}@T{
|
||||
|
@ -200,7 +285,7 @@ Name
|
|||
ClassName
|
||||
Priority
|
||||
TestCategory
|
||||
| | Xunit |
|
||||
| | xUnit |
|
||||
FullyQualifiedName
|
||||
DisplayName
|
||||
Traits
|
||||
|
@ -248,7 +333,7 @@ Expressions can be joined with conditional operators:
|
|||
.PP
|
||||
.TS
|
||||
tab(@);
|
||||
c c.
|
||||
l l.
|
||||
T{
|
||||
Operator
|
||||
T}@T{
|
||||
|
@ -256,7 +341,7 @@ Function
|
|||
T}
|
||||
_
|
||||
T{
|
||||
| \ \
|
||||
|
|
||||
T}@T{
|
||||
OR \ \ \
|
||||
T}
|
||||
|
@ -269,7 +354,7 @@ T}
|
|||
.PP
|
||||
You can enclose expressions in parenthesis when using conditional operators (for example, \f[C](Name~TestMethod1)\ |\ (Name~TestMethod2)\f[]).
|
||||
.PP
|
||||
For additional information and examples on how to use selective unit test filtering, see Running selective unit tests.
|
||||
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
|
||||
.SS See also
|
||||
.PP
|
||||
Frameworks and Targets
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue