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-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,14 +171,19 @@ You can generate a coverage report for a test run through [Erlang Cover](http://
171
171
Coverage information for all **current** code run on any Riak node started by any of the tests in the run will be output as HTML in the coverage directory.
172
172
That is, legacy and previous nodes used in the test will not be included, as the tool can only work on one version of the code at a time.
173
173
Also, cover starts running in the Riak nodes after the node is up, so it will not report coverage of application initialization or other early code paths.
174
-
You can specify a list of modules for which you want coverage generated like this:
174
+
Each test module, via a module attribute, can specify what modules it wishes to cover compile:
To enable this, you need to turn coverage in in your riak_test.config:
183
+
```erlang
184
+
{cover_enabled, true}
185
+
```
186
+
Tests that do not include coverage annotations will, if cover is enabled, honor {cover_modules, [..]} and {cover_apps, [..]} from the riak_test config file.
182
187
183
188
#### Web hooks
184
189
When reporting is enabled, each test result is posted to [Giddy Up](http://giddyup.basho.com). You can specify
0 commit comments