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
@@ -115,11 +115,17 @@ If you are running into a scenario where your tests normally pass, but fail when
115
115
* timing issues on futures and other async operations, try upping the timeouts by an order of magnitude.
116
116
* tests are run in a sandbox mode (such as with `java.security.PrivilegedAction<T>`), try running the tests outside of the sandbox.
117
117
118
-
## Coveralls
118
+
## Integrations
119
+
120
+
### Codacy
121
+
122
+
[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).
123
+
124
+
### Coveralls
119
125
120
126
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.
121
127
122
-
## Plugin for SonarQube
128
+
###Plugin for SonarQube
123
129
124
130
If you want to visually browse statement coverage reports then use this [plugin for SonarQube](https://github.com/RadoBuransky/sonar-scoverage-plugin).
125
131
It allows you to review overall project statement coverage as well as dig deeper into sub-modules, directories and
0 commit comments