Hi
Any plans for supporting any of the new reporting features in NCover 3.3? Like the trend report?
Regards,
Michael
Hi Michael,
What are the new command line options that allow you to use the new reporting features in 3.3? I’ve had a quick look at the NCover website and couldn’t find which features and command line arguments are new in 3.3.
Regards,
Paul.
At first I just looked at the userinterface and saw all the new reports you can generate. I now see that there is a new executable called ncover.reporting.exe which allow for the new reporting including trends.
Below you see the usage help for ncover.reporting.exe. So basically its the trend data I am after.
Arguments: NCover.Reporting.exe
NCover.Reporting [inputfiles] [options]
Processes a set of NCover coverage xml files from the _output.
Intended for usage in automated builds.
Options:
//at[appendTrend]
Append trend data from merged coverage files to the given file.
//bi[buildId]
Specify the build ID of the coverage data saved with the //s argument.
Defaults to the build id of the first coverage file loaded.
//cr[configRead] (This switch may be used more than once)
Path to a settings file that provides an isolated reporting context.
Every parameter before the first //cr switch belongs to the first
configuration processed, and the //cr switch creates a second configuration
(unless //cr is the first argument, in which case it is the first
configuration).
Every paramter after a //cr switch and before the next //cr switch
overwrites (or appends, for switches that can be specified multiple times)
the appropriate values in the configuration for that execution.
//cs[configSave]
Path to save the current settings file to.
This parameter is ignored if more than one //cr switch is used.
//ccf
Clear the existing coverage filters on the view.
//cf[coveragefilter] (This switch may be used more than once)
Specifies a filter to run against the coverage data.
If not specified, filters are taked from the first
loaded coverage data file.
Format: //cf filterdata[:item type][:isRegex][:isInclude]
'filterdata' is the pattern the filter uses to match elements
'item type' is the type of element the filter matches
Possible Values: "Assembly", "Namespace", "Class", "Method", "Document"
'isRegex' when true the 'filterdata' is interpreted as
a regular expression, when false it is interpreted as a wildcard
(default is false)
'isInclude' when true elements that don't match the filter are
excluded, and when true, elements that match the filter are excluded
(default is false)
//hi[hide]
Specify what elements to hide if any for the report
None (default)
HideUnvisited
HideFullyCovered
HideThresholdCovered
//ifb[ignorefailedbuilds]
When displaying trend graphs, whether to include or exclude builds with fail
ing tests.
//lt[loadTrend]
Load trend data for the reports from the given filename and directory.
//mfm
Determines how to handled the filters of a coverage file during merge operat
ions.
Default or KeepSourceFilters - Keep First file filters and purge excluded no
des from other files.
Destructive - Remove all excluded items from all files and remove all filter
s.
AppendFilters - Keep all of the nodes and append all of the filters to the f
irst file.
//mc (This switch may be used more than once)
Fails the build if the coverage on the specified item type is
less than the given coverage.
Format:
//mc Coverage Metric[:Min Coverage Value][:Item Type][attern]
Coverage Metric:
SymbolCoverage
BranchCoverage
MethodCoverage
LineCoverage
CyclomaticComplexity
Item Type:
(default= View)
Assembly
Namespace
Class
Document
Examples:
Fails satisfactory coverage if the method coverage of any class dips below
34.5%
//sct MethodCoverage:34.5:Class
Fails satisfactory coverage if the maximum cyclomatic complexity
of namespace 'Ergo.Unit.Tests' is above 20
//sct CyclomaticComplexity:20:Namespace:Ergo.Unit.Tests
//smf[showMaxFailed]
Controls how many items that fail the //mc rules will
be displayed on the _output. Default is 50.
//so[sort]
Specify the sorting if any for the report (default = None)
Name
ClassLine
CoveragePercentageAscending
CoveragePercentageDescending
UnvisitedSequencePointsAscending
UnvisitedSequencePointsDescending
VisitCountAscending
VisitCountDescending
FunctionCoverageAscending
FunctionCoverageDescending
//tu[topuncovered]
Specify the number of uncovered items to show
in the top uncovered reports.
//q[quiet]
Minimise the console message output
//xslt
Provide an override Xslt file for reporting.
//? or //help
Displays this help
All reports succeeded.
I now see that its the same as NCoverExplore.console.exe