com.unity.testtools.codecoverage 1.2.0

com.unity.testtools.codecoverage

Notes: processedReleased August 24, 2022

Browse versions

PreviousNext

Unity Compatibility

Minimum Unity: 2019.3 (0a8)

🔧 Bug Fixes

  • Ensure assemblies are removed from the Included Assemblies field if they no longer exist (case 1318668).
  • Ensure hidden sequence points are ignored (case 1372305).

🔄 Changes

  • Updated Report Generator to version 5.0.4.
  • Updated the UI of the Code Coverage window moving the action buttons into a toolbar at the top.
  • Renamed *assemblyFilters* aliases in batchmode; `` was renamed to `` and `` was renamed to ``.
  • Replaced `pathStrippingPatterns` with `pathReplacePatterns` in batchmode. The `pathReplacePatterns` option allows stripping and replacing specific sections from the paths that are stored in the coverage results xml files.
  • See the Upgrade guide if upgrading to Code Coverage package version 1.2.

📈 Improvements

  • The size of the coverage result files and the Code Coverage session duration have been optimized. At the start of the session a coverage xml result file is generated which includes all the lines but with zero coverage. The following coverage xml result files that are generated within a Code Coverage session include only the coverage data of the visited lines.
  • Added Help IconButton in the toolbar in the Code Coverage window.
  • Updated the mechanic for opening the containing folder, change the location or reset to the default location for *Results Location* and *Report History Location*.
  • Refactored the Code Coverage window UI to include a new *Report Options* section and removing the word 'Generate' from the options.
  • Introduced new selection buttons under the *Included Assemblies* dropdown in the Code Coverage window; use the *All* button to select all the assemblies in the project. Use the *Assets* button to select only the assemblies under the `Assets` folder. Use the *Packages* button to select only the Packages' assemblies. If searching, the buttons will apply only to the assemblies visible in the list.
  • Updated What's new and Upgrade guide pages in the documentation.
  • Added Using relative paths in path filters section in documentation.
  • Updated the editor and console logs; added information about the assembly and path filters, improved coverage session logs.
  • Improved the progress bars for `Writing coverage results` and `Generating the report`.
  • Added an icon for the Code Coverage window.
  • Updated documentation to match version 1.2.0.

Features

  • Added `Pause Recording` and `Resume Recording` buttons in the toolbar in the Code Coverage window.
  • Added `Log Verbosity Level` setting in the Code Coverage window which allows setting the verbosity level for the editor and console logs.
  • Added `Additional Reports` option in the Code Coverage window which if checked SonarQube, Cobertura and LCOV reports will be generated. Added `generateAdditionalReports` in *-coverageOptions* for batchmode.
  • Added `Test Runner References` report option in the Code Coverage window which if checked includes test references to the generated coverage results and enables the Coverage by test methods section in the HTML report, allowing you to see how each test contributes to the overall coverage. Added `generateTestReferences` in *-coverageOptions* for batchmode.
  • Added `Auto Open Report` option in the Code Coverage window which if checked the coverage report will open automatically after it has been generated.
  • Added `pathFiltersFromFile` in *-coverageOptions* for batchmode which allows specifying an external file which contains a list of path filters. When this file contains relative paths, the `sourcePaths` option can be used to specify the source directories.
  • Added `dontClear` in *-coverageOptions* for batchmode which allows coverage results to be accumulated after every code coverage session. If not passed the results are cleared before a new session. For more information see Generate combined report from EditMode and PlayMode tests.
  • When the `pathFilters` option or the `pathFiltersFromFile` option in *-coverageOptions* contains relative paths, the `sourcePaths` option can be used to specify the source directories.