sbt-unidoc
sbt-scoverage
sbt-unidoc | sbt-scoverage | |
---|---|---|
- | 2 | |
124 | 638 | |
-2.4% | -0.2% | |
6.3 | 6.9 | |
2 months ago | about 1 month ago | |
Scala | Scala | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sbt-unidoc
We haven't tracked posts mentioning sbt-unidoc yet.
Tracking mentions began in Dec 2020.
sbt-scoverage
-
Code coverage reporting incorrect in InteliJ, is there a solution that can determine code coverage correctly for Scala?
I use this: https://github.com/scoverage/sbt-scoverage
-
Newbie at coding & testing. Feel ashamed of asking these questions...
Adding to all the excellent comments here, if you want to get an idea of where to get started, a report from coverage analysis or (personal plug) mutation testing can give you insight for where to start
What are some alternatives?
mdoc - Typechecked markdown documentation for Scala
ScalaKata2 - Interactive Playground
sbt-mima-plugin - A tool for catching binary incompatibility in Scala
sbt pom reader plugin - Translates xml -> awesome. Maven-ish support for sbt.
sbt-pack - A sbt plugin for creating distributable Scala packages.
sbt-doctest - Doctest for scala
sbt-revolver - An SBT plugin for dangerously fast development turnaround in Scala
JMH - "Trust no one, bench everything." - sbt plugin for JMH (Java Microbenchmark Harness)
sbteclipse - Plugin for sbt to create Eclipse project definitions
sbt-ci-release - sbt plugin to automate Sonatype releases from GitHub Actions