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
Then run the your tests with coverage enabled by entering:
@@ -58,7 +58,11 @@ Next, the keys have been renamed slightly. The new names begin with coverageXXX,
58
58
59
59
## Multi project reports
60
60
61
-
By default, scoverage will generate reports for each project seperately. You can merge them into an aggregated report by invoking `sbt coverageAggregate`. Note, you must do this after all the coverage data is complete as a separate command, so you cannot do `sbt coverage test coverageAggregate` (at least until a way around this is found).
61
+
By default, scoverage will generate reports for each project seperately. You can merge them into an aggregated report by invoking `sbt coverageAggregate`.
62
+
63
+
(Note, you must do this after all the coverage data is complete as a separate command, so you cannot do `sbt coverage test coverageAggregate` (at least until a way around this is found).)
64
+
65
+
(You must have first run `sbt coverageReport` for `coverageAggregate` to work. It aggregates over the sub-projects' report xml rather than over the coverage data directly.)
62
66
63
67
## Exclude classes and packages
64
68
@@ -94,6 +98,9 @@ coverageMinimum := 80
94
98
coverageFailOnMinimum :=true
95
99
```
96
100
101
+
These settings will be enforced when the reports are generated.
102
+
If you generate an aggregate report using `coverageAggregate` then these settings will apply to that report.
103
+
97
104
## Highlighting
98
105
99
106
If you are using Scala 2.11.1 or less, then highlighting will not work (due to this bug which was fixed in 2.11.2 https://github.com/scala/scala/pull/3799). In that case you must disable highlighting by adding the following to your build:
0 commit comments