...
| Info | ||||
|---|---|---|---|---|
| ||||
dotTEST can collect coverage for .NET Core standalone applications (configuring additional dependencies with the dedicated environment variable or the dotnet.exe command line switch |
| Info | ||||
|---|---|---|---|---|
| ||||
You can leverage the capabilities of the the Note: In typical workflows, dotTEST collects coverage for web applications deployed on IIS server (see Application Coverage for Standalone Applications). |
| Anchor | ||||
|---|---|---|---|---|
|
Run the
[INSTALL_DIR]\coverage.exetool and specify the following information:
- Full path to the application
- Command line arguments
- Working directory
Info icon false title Collecting coverage for a .NET Core web application Complete the Full path to the application field with the path to
dotnet.exeand the Command line arguments field with the entry point of the application. For example:
- Specify the .NET CLR version used by the application.
- Specify a directory where the scripts generated by the wizard will be saved.
Specify if you want to collect coverage information with or without the Coverage Agent:
- If you enable the Use Coverage Agent option, enable or disable the Collect coverage without admin privileges option (see Collecting Coverage without Admin Privileges), then skip steps 5-7 and click Finish.
- If you enable the Without Coverage Agent option (default), proceed to steps 5-7.- Define the scope of coverage to import by providing
-solutionor-projectswitches that will be passed to the dotTEST executable so that it can locate sources. See Configuring the Test Scope for more information about the switches. Enable or disable the Remove old coverage data before each run option. This option is enabled by default.
Info By default, dynamic coverage information that was collected during previous executions is deleted. Disabling this option will prevent removing the data from previous runs.
- Enable or disable the Run application immediately option to automatically launch the
monitorCoverage.batscript ( if enabled, the application must be manually launched with the script generated by the wizard in the location specified in step 3).
...