sbt-scoverage
JMH
Our great sponsors
sbt-scoverage | JMH | |
---|---|---|
2 | 3 | |
637 | 782 | |
0.0% | 0.1% | |
7.1 | 7.0 | |
27 days ago | 5 days 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-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
JMH
-
Scala collections benchmark - revisited
Also, it has an amazing SBT plugin integration.
-
Why is Scala so much slower than JavaScript/Node at running iterations?
Take a look at sbt-jhm for doing benchmarks. Java in particular is hard to measure because of optimizations that happen at run-time. jhm runs multiple iterations and gives tools to ensure that function calls and loops that may be optimized away are kept around and tested. You may also find some cases that are faster in node.js because the Javascript V8 engine is highly optimized.
-
Help with making backtracking more efficient
Also, if you really want to know what the performance characteristics are you should use JMH (sbt plugin https://github.com/sbt/sbt-jmh). Not sure how you are evaluating the performance but things like JVM startup and warming can make a big difference. JMH will give you a better idea of real world performance when the JVM is already started and any relevant hot code has been JIT compiled.
What are some alternatives?
ScalaKata2 - Interactive Playground
JITWatch - Log analyser / visualiser for Java HotSpot JIT compiler. Inspect inlining decisions, hot methods, bytecode, and assembly. View results in the JavaFX user interface.
sbt pom reader plugin - Translates xml -> awesome. Maven-ish support for sbt.
honest-profiler - A sampling JVM profiler without the safepoint sample bias
sbt-doctest - Doctest for scala
Sniffy - Sniffy - interactive profiler, testing and chaos engineering tool for Java
sbt-mima-plugin - A tool for catching binary incompatibility in Scala
LatencyUtils - Utilities for latency measurement and reporting
sbt-revolver - An SBT plugin for dangerously fast development turnaround in Scala
sbt-sonatype - A sbt plugin for publishing Scala/Java projects to the Maven central.
sbt-ci-release - sbt plugin to automate Sonatype releases from GitHub Actions
jHiccup - jHiccup is a non-intrusive instrumentation tool that logs and records platform "hiccups" - including the JVM stalls that often happen when Java applications are executed and/or any OS or hardware platform noise that may cause the running application to not be continuously runnable.