You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-2Lines changed: 8 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -120,11 +120,17 @@ If you are running into a scenario where your tests normally pass, but fail when
120
120
* timing issues on futures and other async operations, try upping the timeouts by an order of magnitude.
121
121
* tests are run in a sandbox mode (such as with `java.security.PrivilegedAction<T>`), try running the tests outside of the sandbox.
122
122
123
-
## Coveralls
123
+
## Integrations
124
+
125
+
### Codacy
126
+
127
+
[Codacy](https://www.codacy.com) integrates with your favorite coverage tool to provide an in-depth overlook of your project status. Scoverage information can be integrated into Codacy through the [sbt-codacy-coverage plugin](https://github.com/codacy/sbt-codacy-coverage).
128
+
129
+
### Coveralls
124
130
125
131
If you have an open source project then you can add code coverage metrics with the excellent website https://coveralls.io/ Scoverage will integrate with coveralls using the [sbt-coveralls](https://github.com/scoverage/sbt-coveralls) plugin.
126
132
127
-
## Plugin for SonarQube
133
+
###Plugin for SonarQube
128
134
129
135
If you want to visually browse statement coverage reports then use this [plugin for SonarQube](https://github.com/RadoBuransky/sonar-scoverage-plugin).
130
136
It allows you to review overall project statement coverage as well as dig deeper into sub-modules, directories and
0 commit comments