Releases: scoverage/sbt-scoverage
v2.0.0-M1
This is the first Milestone release supporting the 2.x series of scoverage. For existing 2.12 and 2.13 users nothing should have really changed for you from a users standpoint. You can find more context to what this release means here in the main repo. Keep in mind that this tag is attached to the V2 branch, not main.
NOTE: that once the pr into lampepfl/dotty
is created for coverage support in Scala 3 this version will already be able to be used with a self-published 3.1.2-RC1-bin-SNAPSHOT
version of Scala, which needs to be published locally, until it's merged in and released.
Towards coverage support in Scala 3!
v1.9.1
What’s Changed
- Ensure reporting and aggregation still works when disabling modules. (#377) @ckipp01
- Update scalafmt-core to 3.0.6 (#375) @scala-steward
- Update sbt-ci-release to 1.5.9 (#373) @scala-steward
- Update scalafmt-core to 3.0.4 (#371) @scala-steward
v1.9.0
What’s Changed
- Update default scoverage to 1.4.9 (#370) @ckipp01
- provide possibility to set up data dir(Rebased to newest version) (#366) @pzhong-livongo
- Update scalafmt-core to 3.0.3 (#367) @scala-steward
- Update scalafmt-core to 3.0.2 (#365) @scala-steward
- Update scalafmt-core to 3.0.1 (#364) @scala-steward
- Update scalafmt-core to 3.0.0 (#363) @scala-steward
- Update sbt, scripted-plugin to 1.5.5 (#361) @scala-steward
- Update sbt-scalafmt to 2.4.3 (#359) @scala-steward
- Update sbt, scripted-plugin to 1.5.4 (#357) @scala-steward
- Update to scala 2.12.14 (#356) @samupra
- Update sbt, scripted-plugin to 1.5.3 (#355) @scala-steward
sbt-scoverage v1.8.2
What’s Changed
- Update scalac-scoverage-plugin to 1.4.8 (#354) @scala-steward
sbt-scoverage v1.8.1
sbt-scoverage v1.8.0
The v1.8.0 release is the first release in a while to bring some new
features!
One thing you may have noticed in the past was some confusion around how
coverageMinimum
was calculated. For example you would often see something like
the following:
// build.sbt
coverageMinimum := 80
Then you'd run your tests, and the output would be as follows:
[info] Statement coverage.: 81.00%
[info] Branch coverage....: 70.00%
[info] Coverage reports completed
[info] All done. Coverage was [81.00%]
You may be wondering how does that equate to 81%? There has been quite a few
issues reported in the past that referred to the average not being correct.
However, the coverageMinimum
is not an actual average, but simply the
statement coverage. So while branch coverage is shown, it has no effect on the
actual percentage used to fail your build or to show you your end coverage
percentage. This is part of the reason why we've decided to deprecate
coverageMinimum
in favor of coverageMinimumStmtTotal
to make this clearer.
Another reason is due to the newly added more fine-grained controls you have for
coverage totals thanks to the great work by @kitbellew. Now we are able to
have much finer control over the various totals with the introduction of some
new setting keys that can all be used to fail your build:
coverageMinimumStmtTotal := 90
coverageMinimumBranchTotal := 90
coverageMinimumStmtPerPackage := 90
coverageMinimumBranchPerPackage := 85
coverageMinimumStmtPerFile := 85
coverageMinimumBranchPerFile := 80
New Features
- Coverage minima: add more fine-grained control (#253) @kitbellew
- Report test names (#297) @vincentdehaan
- Added TeamCity branch coverage reporting (#258) @alexnikitchuk
Bug Fixes
Housekeeping
- Bump scoverage version to 1.4.6 (#349) @ckipp01
- Update sbt, scripted-plugin to 1.5.2 (#348) @scala-steward
- Update tests in scripted. (#347) @ckipp01
- Overhaul the README (#346) @ckipp01
- Add in Scalafmt (#344) @ckipp01
- Remove local snapshot version (#343) @ckipp01
Big thanks to everyone that made this release possible!
v1.7.3
v1.7.2
sbt-scoverage v1.7.1
Small release adding support for the latest scoverage 1.4.4
sbt-scoverage v1.7.0
coverageCleanSubprojectFiles
key has been removed- No longer cross sbt published. sbt 1.2.8 is now required
- Only support for Scala 2.12+ versions.