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
Import .coverdata after test run and improve documentation (#309)
* Import `.coverdata` after test run and improve docs
* Update README table of contents
* Update README based on review suggestion
Co-authored-by: Alberto Sartori <[email protected]>
---------
Co-authored-by: Alberto Sartori <[email protected]>
ExCoveralls can include `.coverdata` files in the result of the current test run through the `--import-cover` flag. This can be used to include coverage data from partitioned tests or integration tests that may run in a subprocess, for instance.
515
+
516
+
Coverage data is generated when running `mix test --cover`, optionally with the `--export-coverage` flag to specify an output name.
517
+
518
+
```shell
519
+
$ mix test --only integration --cover --export-coverage integration-coverage
520
+
Excluding tags: [:test]
521
+
Including tags: [:integration]
522
+
... test run omitted ...
523
+
# Coverage data written to cover/integration-coverage.coverdata
524
+
525
+
# Report coverage, do not run integration tests
526
+
$ mix coveralls --exclude integration
527
+
Excluding tags: [:integration]
528
+
... test run omitted ...
529
+
530
+
----------------
531
+
COV FILE LINES RELEVANT MISSED
532
+
...
533
+
[TOTAL] 80.2% # <-- This result does not include coverage from integration tests
534
+
----------------
535
+
536
+
# Report coverage, do not run integration tests, but include previously written coverdata
0 commit comments