Skip to content

Releases: SteveGilham/altcover

Caba series Release 4

10 Apr 16:38
Compare
Choose a tag to compare

3.0.404

  • Exclusion by attribute on a class also extends to all nested classes, including invisible ones like lambda expressions and relatives.
  • Runner mode (and the AltCover.Collect task) now outputs coverage summaries (class, method, point and, where available, branch)
  • -l|lcovReport option in runner mode (parameter LcovReport for the AltCover.Collect task) to also output the result in lcov format

Caba series Release 3

08 Apr 11:07
Compare
Choose a tag to compare

3.0.400 (Caba series release 3)

  • [BUGFIX] -- malformed filter regexes no longer cause a crash, but are reported as normal errors
  • F# auto-properties are now omitted from coverage, just as C# ones are (and have been since before v1.0.101)
  • [BUGFIX] -- errors during the instrumentation or collection phases are actually reported
  • The main AltCover assembly also now publishes MSBuild tasks AltCover.Prepare and AltCover.Collect; the former is the normal mode with --opencover --save --inplace as default, the latter is runner mode with --collect as default. The full parameter lists are
InputDirectory
OutputDirectory
SymbolDirectories†
Keys†⁋
StrongNameKey⁋
XmlReport
FileFilter†
AssemblyFilter†
AssemblyExcludeFilter†
TypeFilter†
MethodFilter†
AttributeFilter†
CallContext†
OpenCover‡
InPlace‡
Save‡
CommandLine

where these parameters are all optional strings (default empty) except as noted
† = optional array of strings, default empty
‡ = Boolean, default true
⁋ = Mono/.net Framework build only

and

RecorderDirectory⸸
WorkingDirectory
Executable

CommandLine

with all these parameters being optional strings (default empty) except as noted
⸸ denotes a [Required] parameter

The task parameters match the command line arguments in name and function, except that SymbolDirectories is pluralised, and CommandLine is everything after a --. If AltCover.Collect's Executable parameter is set, that switches the virtual --collect flag off.

Caba series Release 2

03 Apr 09:09
Compare
Choose a tag to compare

3.0.388

  • Improved command line error reporting
  • --inplace option to instrument the assemblies in the input directory, having saved them to the output directory first; this avoids the manual copy-back step for dotnet test and the like
  • --save option in instrumenting mode plus --collect in runner mode; --save sets the instrumented assemblies to record coverage to disk, just as the runner mode does; then after doing whatever is required with the instrumented code, runner --collect will process the output just as if the operations had been run from within AltCover runner. Note that if --collect is set, any arguments after a -- are ignored.

Caba series Release 1

01 Apr 09:27
Compare
Choose a tag to compare
Caba series Release 1 Pre-release
Pre-release

3.0.367-pre

  • [BREAKING CHANGE] -- packaging the .net core as binaries -- so dotnet AltCover.dll rather than dotnet run altcover.core.fsproj to invoke. This will be needed to do the MSBuild integration that's in the pipeline, where it isn't for a simple command-line tool
  • [BUGFIX] -- calculate branch exit visit count for --opencover (an oversight in 2.0.360)

Byakko series Release 7

30 Mar 14:48
Compare
Choose a tag to compare

2.0.360

  • Branch coverage for --opencover. Note that AltCover takes a rather more conservative approach to detecting "significant" branch points than does OpenCover : it excludes all branches that are entirely internal to a reported sequence point in the source (thus eliminating the many and various sorts of compiler-surprise hidden branching that may include sequence points with no corresponding source location); additionally, if two or more exits from a branch go to the same place, they are considered to constitute only one branch-point in the report, rather than being counted separately.
  • Bonus feature -- -c|callContext tracking also applies to branch visits
  • Also take the latest VS2017 and FAKE updates for building

Byakko series Release 6

24 Mar 12:57
Compare
Choose a tag to compare

2.0.354

No functional changes this release, just updates of consumed components and tooling

  • Take the Cecil 0.10.0 final release, having worked around the issues with unit testing in .net core with NUnit3TestAdapter 3.10, which links the beta6 version, which has a subset of the internal API present in the full release.
  • Take the latest VS2017 and FAKE updates for building

Byakko series Release 5

23 Mar 18:26
Compare
Choose a tag to compare

NOTE: The main executable still links the Mono.Cecil 0.10-beta7 version, as the 0.10 final version causes issues with some build tools that haven't caught up with events. The binary injected into the instrumented code does not link Cecil at all. Until the wrinkles are ironed out or worked around, I make this disclaimer instead.

2.0.350

  • -c|callContext option to track (when collecting the coverage data in "runner" mode) what led to a particular line of code being visited -- either by being called from a method of a specified name or with a specified attribute (unit testing, in the main), or by time of visit (which would be more appropriate for system testing). Methods (typically, unit tests) may be tracked even if they are in assemblies that are excluded from instrumentation via the -ecommand line parameter.

Byakko series Release 4

13 Mar 14:01
Compare
Choose a tag to compare

NOTE: The main executable links the still in beta (after more than a year) Mono.Cecil 0.10 version. The binary injected into the instrumented code does not. Rather than hold my releases on the Mono.Cecil schedule, I make this disclaimer instead.

2.0.330 (Byakko series release 4)

  • "y|symbolDirectory=" option to provide other locations to find symbols for the instrumented assemblies. The search order goes -- location in the debug header, co-located (.pdb than .mdb), then supplied locations tested in order for .pdb than .mdb

Byakko series Release 3

10 Mar 14:05
Compare
Choose a tag to compare

NOTE: The main executable links the still in beta (after more than a year) Mono.Cecil 0.10 version. The binary injected into the instrumented code does not. Rather than hold my releases on the Mono.Cecil schedule, I make this disclaimer instead.

2.0.324 (Byakko series release 3)

  • Option --opencover now generates values for MethodPoint tags when collecting the coverage data in "runner" mode
  • When a process is launched from altcover, the command line is now echoed to stdout
  • Build changes : Visual Studio 15.6.1, and latest FAKE 5 beta releases (beta 24); modified the full-framework builds to emit portable .pdb files on Mono, so the travis-ci tests now get coverage for the framework build
  • [BUGFIX] altcover.core.fsproj will now build if the Platform is set (previously only AnyCPU, explicitly or by default, would work)
  • Other x86 related information added to the wiki

Byakko series Release 2

02 Mar 11:04
Compare
Choose a tag to compare

NOTE: The main executable links the still in beta (after more than a year) Mono.Cecil 0.10 version. The binary injected into the instrumented code does not. Rather than hold my releases on the Mono.Cecil schedule, I make this disclaimer instead.

2.0.300 (Byakko series release 2)

  • [BUGFIX] OpenCover format output now works correctly when classes or methods are filtered out of the coverage
  • Option --opencover now generates cyclomatic complexity values while generating the report file
  • Option --opencover now generates roll-up statistics "visitedSequencePoints", "visitedMethods", "visitedClasses", "sequenceCoverage" in Summary tags, and "visited", "sequenceCoverage" in Method tags when collecting the coverage data in "runner" mode