Analysis updated 2026-08-07 · repo last pushed 2019-06-13
Find untested code paths in your Scala application before shipping.
Verify that your tests cover every branch in functions with if/else conditions.
Generate HTML reports showing which code is covered green and uncovered red.
Exclude specific packages or code sections from coverage measurement using special comments.
| jiminhsieh/scalac-scoverage-plugin | cakiki/database | janikdotzel/akka-http-quickstart-scala | |
|---|---|---|---|
| Language | Scala | Scala | Scala |
| Last pushed | 2019-06-13 | 2026-03-13 | 2023-05-19 |
| Maintenance | Dormant | Maintained | Dormant |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 2/5 | 2/5 |
| Audience | developer | researcher | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a Scala build tool like sbt, Maven, or Gradle to wire the plugin into your project, you don't use it directly.
scalac-scoverage-plugin is a free tool that helps Scala developers see how much of their code is actually tested. It generates detailed reports showing which statements and branches (the different paths code can take, like if/else conditions) were executed during test runs, and which were skipped. When tests run, the tool watches which lines of code get triggered and which don't, then produces an HTML report that highlights covered code in green and uncovered code in red. What makes this approach different is its focus on statement coverage rather than line coverage. Because Scala lets you pack multiple statements onto a single line, traditional line-by-line metrics can be misleading. A single line might contain a branch, and if your test only exercises one path, you'd see 100% line coverage while actually missing half the logic. By counting individual statements, it gives a more accurate picture of what's genuinely tested. A team building a Scala application would use this to keep their test suite honest. For example, if you have an age-check function that returns different messages depending on the user's age, the tool shows whether your tests actually try every age bracket. If half the branches are never hit, you know your tests have gaps before you ship. This repository is the core engine, a plugin that hooks into the Scala compiler. In practice, you wouldn't use this directly, instead, you'd add it through build tools like sbt, Maven, or Gradle, which wire it into your project automatically. You can also exclude specific packages or mark sections of code with special comments to skip coverage measurement on things you don't want counted.
A free Scala tool that measures how much of your code is actually tested by tracking individual statements and branches, then generates HTML reports showing covered and uncovered code in green and red.
Mainly Scala. The stack also includes Scala, sbt, Maven.
Dormant — no commits in 2+ years (last push 2019-06-13).
Free and open-source tool for measuring Scala code test coverage, license details are not specified in the provided explanation.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.