Closed nkbt closed 9 years ago
ping @forresst
LGTM. This works great on windows.
The output is a little different for npm run test:dev
Here are the results of my tests :
c:\lab\cf-package>npm test
> cf-package@1.0.0 test c:\lab\cf-package
> babel-node node_modules/blue-tape/bin/blue-tape test/**/*-test.js
TAP version 13
# Generate
ok 1 should be function
ok 2 should return function
ok 3 should fill template with values
ok 4 should fill multiple templates with values
# Parse props
ok 5 should be function
ok 6 should return function
ok 7 should parse dot-delimited props into nested objects
ok 8 should merge parsed data into defaults object
1..8
# tests 8
# pass 8
# ok
> cf-package@1.0.0 precov c:\lab\cf-package
> rimraf coverage
> cf-package@1.0.0 cov c:\lab\cf-package
> babel-node node_modules/isparta/bin/isparta cover --report text --report html
test
TAP version 13
# Generate
ok 1 should be function
ok 2 should return function
ok 3 should fill template with values
ok 4 should fill multiple templates with values
# Parse props
ok 5 should be function
ok 6 should return function
ok 7 should parse dot-delimited props into nested objects
ok 8 should merge parsed data into defaults object
================================================================================
Writing coverage object [c:\lab\cf-package\coverage\coverage.json]
Writing coverage reports at [c:\lab\cf-package\coverage]
================================================================================
----------------|----------|----------|----------|----------|----------------|
File | % Stmts | % Branch | % Funcs | % Lines |Uncovered Lines |
----------------|----------|----------|----------|----------|----------------|
lib\ | 100 | 100 | 100 | 100 | |
generate.js | 100 | 100 | 100 | 100 | |
parseProps.js | 100 | 100 | 100 | 100 | |
----------------|----------|----------|----------|----------|----------------|
All files | 100 | 100 | 100 | 100 | |
----------------|----------|----------|----------|----------|----------------|
=============================== Coverage summary ===============================
Statements : 100% ( 49/49 ), 20 ignored
Branches : 100% ( 20/20 ), 13 ignored
Functions : 100% ( 10/10 ), 1 ignored
Lines : 100% ( 8/8 )
================================================================================
> cf-package@1.0.0 test:dev c:\lab\cf-package
> npm test | faucet
V Generate
V Parse props
# tests 8
# pass 8
V ok
I'm using Cmder (ConEmu + Clink), which is at least bearable under Win to some extent. So it might have a little better support of CLI functionality.
Yes ! It's certain ! But it is not a problem, it works correctly.
I've run every npm script on my Win machine and they all work fine now.
Here are results of previously failing ones:
npm test
npm run cov
npm run test:dev