Bump altcover from 6.1.708 to 7.6.812

[dependabot-preview]

Bumps altcover from 6.1.708 to 7.6.812.

Release notes

Sourced from altcover's releases.

Genbu series release 15

7.6.812

• [VISUALIZER] Move the global tool to the new 0.10 AvaloniaUI release
• Monitor API
  • [BUGFIX] Harden the monitor API TryGetVisitTotals against race conditions in multi-threaded tests
  • Publish the AltCover.Monitor API as API (i.e. under lib/) in the main package altcover as well as in altcover.api (but not in altcover.global; global tools aren't library compatible to be accessed through a package add reference). It's there next to the PowerShell assembly (per altcover ImportModule) if you want to manually link to it, though
  • Support writing unit tests involving the API back to net20 as well as netstandard2.0
• Add --jsonReport option (and equivalents) to output the NCover or OpenCover data in a minified JSON format, like the existing --lcovReport option does for that format. The JSON is a direct map of the XML, with values appropriately typed.
• Add a ConvertTo-CoverageJson cmdlet and a ConvertToJson toolkit API to post-precess existing NCover/OpenCover reports

Genbu series release 14

7.5.809

• [NEW] AltCover.Monitor API to track current coverage from running unit tests. Current implementation requires dotnet test, or other command-line testing with --defer set, in which the cumulative visit numbers are available, rather than everything having been dumped to file instead.
• [BUGFIX] In OpenCover format output, only emit <File /> records relevant to the respective module, not for all source files encountered so far.

Genbu series release 13

• [BUGFIX] In some use cases, the error The "AltCover.ContingentCopy" task was not given a value for the required parameter "FileName". could be provoked by dotnet test (Issue #113)
• Extend to other Build Action types (at least all those that my VS2019 Community Edition was prepared to mention) the "If /p:AltCoverInPlace is not true, then copy all files in the project included as <[Action] Include="./[some subdirectory]/..." with CopyToOutputDirectory of Always or PreserveNewest to the appropriate relative location wrt the intrumented files" behaviour added for the None action in the previous release. File an issue report if you have yet another build action type that you need copying for a not-in-place test scenario.

Genbu series release 12

7.4.807

• [MAYBE BREAKING] Set InPlace default to false uniformly across the API
  • Add dotnet test command line option /p:AltCoverInPlace=true|false (default false)
  • If /p:AltCoverInPlace=true then /p:AltCoverForce=true has its pre-v7.3.805 meaning
  • Wire up "InPlace" to the Fake DotNet.test driver for the above
  • If /p:AltCoverInPlace is not true, then copy all files in the project included as <None Include="./[some subdirectory]/..." with CopyToOutputDirectory of Always or PreserveNewest to the appropriate relative location wrt the intrumented files
  • NB /p:AltCoverInPlace=true will not play well with the concurrent instrument-and-test behaviour of dotnet test [multipletestprojects].sln /p:AltCover="true" --output [commonArtifactsFolder]
• Allow --callContext and --single together, which will log at most one visit per context per location, not just one visit per location

Genbu series release 11a

7.3.806

• [BUGFIX] Handle concurrent instrumentation in the case dotnet test [multipletestprojects].sln /p:AltCover="true" --output [commonArtifactsFolder] -- only changes the .targets file

Genbu series release 11

7.3.805

• Extra detection and removal of compiler generated branches in C# async/await constructs
• Revise the whole dotnet test integration
  • Will support SDK versions back at least to v2.1.809, but v2.1.300 is definitely now out of support due to API changes to the Microsoft.TestPlatform.Build.Tasks.VSTestTask task in the interim
  • Rather than copy/instrument back to $(TargetDir)/clean and copy-back, now instrument to a new directory and test there; there are now no worries about instrumented code ever being in the actual build artifact output directory
  • /p:AltCoverForce=true now simply clears the instrumentation target directory, and gives an informational message only
  • Resolve the instrumentation directory once and only once -- prevents inconsistent handling in the case where command line parameter--output redirects $(TargetDir) part-way through the process
• Some refactoring and other build process improvements

Genbu series release 10

7.3.802

• Add a -qoption for AltCover, given once suppresses informational messages, twice also suppresses warnings and thrice also suppresses errors. Away from the command line, the option is called Verbosity, and is based on System.Diagnostics.TraceLevel -- the default level being Info, with Warning, Error and Off equivalent to -q, -qq and -qqq respectively. For the monent Verbose is the same as Info
• Other minor build process improvements

Genbu series release 9

7.2.801

... (truncated)

Changelog

Sourced from altcover's changelog.

Previously

7.3.806 (Genbu series release 11a)

• [BUGFIX] Handle concurrent instrumentation in the case dotnet test [multipletestprojects].sln /p:AltCover="true" --output [commonArtifactsFolder]

7.3.805 (Genbu series release 11)

• Extra detection and removal of compiler generated branches in C# async/await constructs
• Revise the whole dotnet test integration
  • Will support SDK versions back at least to v2.1.809, but v2.1.300 is definitely now out of support due to API changes to the Microsoft.TestPlatform.Build.Tasks.VSTestTask task in the interim
  • Rather than copy/instrument back to $(TargetDir)/clean and copy-back, now instrument to a new directory and test there; there are now no worries about instrumented code ever being in the actual build artifact output directory
  • /p:AltCoverForce=true now simply clears the instrumentation target directory, and gives an informational message only
  • Resolve the instrumentation directory once and only once -- prevents inconsistent handling in the case where command line parameter--output redirects $(TargetDir) part-way through the process
• Some refactoring and other build process improvements

7.3.802 (Genbu series release 10)

• Add a -qoption for AltCover, given once suppresses informational messages, twice also suppresses warnings and thrice also suppresses errors. Away from the command line, the option is called Verbosity, and is based on System.Diagnostics.TraceLevel -- the default level being Info, with Warning, Error and Off equivalent to -q, -qq and -qqq respectively. For the moment Verbose is the same as Info
• Other minor build process improvements

7.2.801 (Genbu series release 9)

• [BUGFIX] Don't ArgumentNullException when running the --callContext for async feature off the build machine
• [BUGFIX] Refactor to avoid "System.ArgumentException: An item with the same key has already been added. Key: AltCover.Recorder.g/7.2.0.0" that could occur in some rare circumstances while instrumenting code.
• Other minor build process improvements

7.2.800 (Genbu series release 8)

• [BUGFIX] Don't produce invalid IL when --callContext indicates a method with a non-void return (issue #105, and probably #26 too)
• [BUGFIX] Restore application icons, even if they only show in the .exe forms (lost in 7.1.795 if not before)
• [BUGFIX] Add AltCover prefix to MSBuild property names NetCoreEngine, NetStdEngine (global), InputDirectory and OutputDirectory (target-scoped) in the injected .targets file for dotnet test integration.
• [BUGFIX] Let the AvaloniaUI based visualizer roll forwards from netcoreapp2.1 onto later runtimes
• Finer-grained control of the coverage summary output
• When --callContext indicates an async method, then track all calls within the same async flow, and not just in the direct same-thread call stack. Note other out-of-thread calls (Thread.Start, Parallel.Invoke, explict Async-named method invocation, ...) are not tracked.
• Build with net5.0 SDK (modulo work-round for dotnet/fsharp#10442) in net5-only environments
  • Still build AltCover.exe/.dll against net472 for framework support, netcoreapp2.1 for the global tool and netcoreapp2.0 for everywhere else
  • Still build the GTK2 visualizer against net472 for consistency
  • Still build the recorder at net20 and use that assembly everywhere (see F# compiler issue noted above) except where a net46 version is substituted for tracking through async calls
  • Move unit tests to net5.0, as they are not public API

7.1.795 (Genbu series release 7)

• [BUGFIX] Make LCov tracefile output follow what is actually generated, and not just what the man page says
• As well as interfaces, hide other types with no non-abstract methods (e.g. plain enums) in the coverage
• Show the branch in public int string Ternary(bool select) => !select ? Left : Right; just like it is shown in public int Ternary (bool select, int left, int right) { return select ? left : right; }.
• For records, add entry and exit attributes as semicolon separated lists of the UTC times in ticks at which the method was entered and returns
• For dotnet test ... /p:AltCoverXmlReport=... , if the value for the report file path contains one of the following literals
  • $(ProjectName)
  • $(SolutionDir)
  • $([System.Guid]::NewGuid())
    then substitute in the actual values of those build parameters where they haven't already been replaced by MSBuild. Example: Using /p:AltCoverXmlReport=$(SolutionDir)/_Reports/solution.$(ProjectName).xml with dotnet test of a solution to place distinctly named report files in a common folder. Also
• Rationalise .net versions to help speed up the build and ease the net5.0 transition
  • Clear out some corner case differences between .net core and .net framework builds based on old work-arounds for symbol writing for the instrumented files

... (truncated)

Commits

• fbfe245 Merge branch 'master' into release/Genbu
• d6b301b [Skip CI] Try again for release
• bb89fe7 See about resolving the AppVeyor anomaly
• 484aac5 Merge branch 'master' into release/Genbu
• b94a0ad [Skip CI] Anticipate release
• 7ba2b3b [Skip CI] Missed these in the move
• 492ac1f Sweep issue 116 under the carpet
• 500a2f5 Fix those tests
• 2cb8315 Test the API separately, not just through the cmdlets
• d0193ce Update release notes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[codecov]

Codecov Report

Merging #75 (db87006) into master (3135650) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #75   +/-   ##
=======================================
  Coverage   36.18%   36.18%           
=======================================
  Files          19       19           
  Lines         152      152           
  Branches        9        9           
=======================================
  Hits           55       55           
  Misses         93       93           
  Partials        4        4           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3135650...db87006. Read the comment docs.

[dependabot-preview]

Superseded by #77.