CodeScene version 6.7.0 includes the following:
- Feature: Code Coverage tab at Software Portfolio
The Software Portfolio now gives a high-level overview of all your projects in terms of CodeScene's four factors and Code Coverage. It is designed to make it easy to see trends impacting your entire organization and to make high-level prioritization.
More information on how the average coverage calculation is done can be found here.
- Added exclusion filters on a project level for Code coverage
Projects will often have only partial code coverage data. This could be for several reasons:
-
- Multiple programming languages in a project: they do not have coverage data yet for one or more of the languages they use
- Multiple repositories: they are currently generating CC data on some repos, but not all
There might also be parts of a codebase that cannot or will not be tested.
All of these situations would lead to many files being marked as having 0% code coverage, in other words as false positives. This would result in an incorrect representation of the code coverage situation, both in terms of which files appear as red 0% files and for the averages that we calculate.
We now have a way for the user to tell CodeScene when the absence of CC data does not mean the absence of code coverage.
If you are running the JAR directly, you can download it here.