Open mstade opened 7 years ago
Merging #49 into master will decrease coverage by
1.55%
. The diff coverage is75%
.
@@ Coverage Diff @@
## master #49 +/- ##
==========================================
- Coverage 95.2% 93.65% -1.56%
==========================================
Files 15 15
Lines 334 315 -19
==========================================
- Hits 318 295 -23
- Misses 16 20 +4
Impacted Files | Coverage Δ | |
---|---|---|
src/cli/opts.js | 100% <100%> (ø) |
:arrow_up: |
src/builder/javascript.js | 96.87% <50%> (-3.13%) |
:arrow_down: |
src/postbuild/rebase-prod-css.js | 16.66% <0%> (-83.34%) |
:arrow_down: |
src/builder/css.js | 100% <0%> (ø) |
:arrow_up: |
src/main.js | 98.98% <0%> (+1.66%) |
:arrow_up: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update d7f110b...72bd495. Read the comment docs.
Description
Code coverage is a staple in code quality assurance – this PR adds code coverage instrumentation to ez-build output so that coverage can be collected on its output.
Motivation and Context
As a developer using ez-build to compile my code, I want the ability to add coverage instrumentation so I can ensure good coverage when implementing tests for my code.
How Was This Tested?
I've added both unit tests for parsing the
--coverage
option and CLI tests for checking that the output is as expected when the option is set and when it's not.Types of changes
Checklist: