Package Exports

lcov-result-merger
lcov-result-merger/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (lcov-result-merger) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

LCOV Result Merger

When you have multiple test suites for the same application you still want to have the code coverage across all testsuites.

This tool will handle this for you.

Usage

./node_modules/.bin/lcov-result-merger 'FILE_PATTERN' ['OUTPUT_FILE']

Examples

Use stdout

Generate LCOV Code Coverage into different files, e.g. build/coverage/coverage_X.log
Run ./node_modules/.bin/lcov-result-merger 'build/coverage/coverage_*.log'
Use the stdout to pipe it to e.g. Coveralls
Done.

Use merged output file

Generate LCOV Code Coverage into different files, e.g. build/coverage/coverage_X.log
Run ./node_modules/.bin/lcov-result-merger 'build/coverage/coverage_*.log' 'target/coverage/coverage_merged.log'
Done. Enjoy your merged file.

Prepend source file paths

Modify source file paths to be relative to the working directory that the merge operation was run in. Useful in monorepos where each child package gathers its own metrics.

./node_modules/.bin/lcov-result-merger 'FILE_PATTERN' ['OUTPUT_FILE'] --prepend-source-files

Since coverage output is rarely written directly into the project root, use --prepend-path-fix to describe the relative path between the lcov file and the project root. The default simply points to one directory up, "..", which works well for common tools such as NYC that write to a /coverage directory.

./node_modules/.bin/lcov-result-merger 'FILE_PATTERN' ['OUTPUT_FILE'] --prepend-source-files --prepend-path-fix "../src"