Installations
npm install separated-coverage
Developer Guide
Typescript
No
Module System
CommonJS
NPM Version
1.4.16
Releases
Unable to fetch releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (95.08%)
HTML (4.92%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
mdevils
Download Statistics
Total Downloads
25,864
Last Day
3
Last Week
23
Last Month
77
Last Year
892
GitHub Statistics
28 Stars
112 Commits
8 Forks
5 Watching
2 Branches
3 Contributors
Package Meta Information
Latest Version
2.3.1
Package Id
separated-coverage@2.3.1
Size
25.23 kB
NPM Version
1.4.16
Total Downloads
Cumulative downloads
Total Downloads
25,864
Last day
-90.3%
3
Compared to previous day
Last week
-39.5%
23
Compared to previous week
Last month
126.5%
77
Compared to previous month
Last year
-34.3%
892
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
separated-coverage
Coverage toolkit designed to collect coverage information separately for each test.
Unlike most coverage tools, separated-coverage
keeps connection between source file and its test file.
For each source file coverage is beeing computed only when its tests are running.
This ensures you have correct test coverage for each file beeing tested.
For example you have file source.js
and its test: source.test.js
.
separated-coverage
collects coverage for source.js
only when source.test.js
is running.
The way source file and test file are beeing linked is configurable.
Installation
npm install separated-coverage --save-dev
Coveralls integration example
First, install coveralls module:
npm install coveralls --save-dev
Create run script for Travis in package.json
. Assuming you are using mocha
, your sources are in lib
directory and tests in test
:
1"scripts": { 2 "test": "...", 3 "travis": "npm test && scov run -q -r lcov -a lib -s 'lib/**/*.js' -a test -t 'test/**/*.js' -- lib test | coveralls" 4}
Change default Travis action from npm test
to npm run travis
in .travis.yml
:
1language: node_js 2script: "npm run travis" 3#...
More about coveralls
: https://coveralls.io/
More about coveralls
npm package: https://github.com/cainus/node-coveralls
CLI Usage
Usage:
scov run [-p <profile>] [-d <driver>] [-b <filename>] [-r <reporter>] [-f <filename>]
[-q] [-A <name>] [-I] [-S <file-set> [-O <name>]...] [-o <filename>]
[-e <mask>]... [-s <mask>]... [-t <mask>]... [-a <mask>]... [-- <runner-args>...]
scov instrument [-p <profile>] [-d <driver>] [-A <name>] [-I] [-q] [-f <filename>]
[-S <file-set> [-O <name>]...]
[-e <mask>]... [-s <mask>]... [-t <mask>]... <path>...
scov report [-p <profile>] [-a <path>]... [-e <mask>]... [-s <mask>]... [-t <mask>]...
[-q] [-S <file-set> [-O <name>]...]
[-r <reporter>] [-o <filename>] <coverage-file>
scov --version
scov --help
Options:
-s --sources=<mask> Source files masks. Example: "lib/**".
-t --tests=<mask> Test files masks. Example: "test/**".
-e --excludes=<mask> Excluded file mask. Example: "lib/**.tmp.js".
-a --additional=<path> Additional files for the coverage report.
Useful when tests do not affect all the files.
-b --bin=<filename> Specifies executable file for test driver.
-d --driver=<driver> Specifies driver [default: mocha].
-r --reporter=<name> Reporer name: html, lcov, summary, teamcity, tree [default: tree].
-o --output=<filename> Report output filename.
-f --file=<filename> Saves "json"-coverage information to specified file.
-X --no-export Do not include json-save action into instrumented file.
-p --profile=<profile> Reads profile from "package.json".
-S --set=<set> File set. Test name source for input files [default: basename].
-O --set-opt <name>=<val> File set option.
-A --api-object-name=<name> Export API to an object in instrumented files.
-I --include-init-coverage Includes initialization coverage information.
-q --quiet Runs quietly.
--help Show this screen.
--version Show version.
![Empty State](/_next/static/media/empty.e5fae2e5.png)
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 2/30 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 2 are checked with a SAST tool
Score
2.6
/10
Last Scanned on 2025-02-03
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More