Info |
---|
The Report Generator action in Continua is a wrapper around the reportgenerator.exe command line. If you're having trouble using the Report Generator action, please refer to the Command Line Reference. |
...
ReportGenerator converts XML reports generated by PartCover, OpenCover or NCover into a readable report in various formats.For more information, including downloads, please visit the ReportGenerator Codeplex page.
ReportGenerator
Name
A friendly name for this action (will be displayed in the actions workflow area).
...
Determines if this action will be run within the relevant stage.
Project Path
Path to project file or folder. If a folder is specified, the folder will be searched for a file that has a file extension that ends in `proj`. Defaults to the workspace folder.
Reports
The coverage reports that should be parsed. Wildcards are allowed. [-reports:]
Target Directory
The directory where the generated report should be savedsaved [-targetdir:]
Report Types
The types of reports that should be generated. [-reporttypes:]
Using
The Using drop down is populated with any property collector whose namespace matches the pattern defined by the ReportGenerator Actionaction. The pattern for this action is ^ReportGenerator\.*
...
Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.
Filters
Filters
List of assemblies that should be included or excluded in the report.
Assembly Filters: [-assemblyfilters:]
Class Filters: [-classfiltters:]
Exclusion filters take precedence over inclusion filters. Wildcards are allowed.
Each filter should begin on a new line.
The following are some examples of the filters format:
+myClass
+myClass.myMethod
-myClass
-*.myMethod
+myClass.*
Options
Source Directories
The directories which contain the corresponding source code. [-searchdirs:]
These are used if the coverage report contains classes without path information.
...
Optional directory for storing persistent coverage information. Can be used in future reports to show coverage evolution. [-historydir:]
Verbosity
The amount of information detail to display in the build log. [-verbosity:]
Timeout (in seconds)
How long to wait for the action to finish running before timing out. Leaving this blank (or zero) will default to 86400 seconds (24 hours).
...
If this is ticked, any warnings logged will not mark the action with a warning status.
Filters
Filters
List of assemblies that should be included or excluded in the report.
Exclusion filters take precedence over inclusion filters. Wildcards are allowed.
Each filter should begin on a new line.
The following are some examples of the filters format:
+myClass
+myClass.myMethod
-myClass
-*.myMethod
+myClass.*
Environment
Environment
Environment Variables
...