-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding test coverage with nyc #622
Conversation
Pattern Lab Node Core 2.7.1
Pattern Lab Node Core 2.7.2
I love the idea of understanding our code coverage and endeavoring to improve it. In your tests, what was the output coverage? 😈 I want to review what tap already comes with to understand if the additional, direct dev dependency is needed. http://www.node-tap.org/coverage/ |
I just used
|
@bmuenzenmeyer Here's the test coverage report when I do
On the 3.0 branch 1 test is failing. same command nyc npm test
|
@benhalverson Is there a reason why we have On that note … "scripts": {
"test": "eslint core/**/*.js && tap test/*_tests.js --reporter spec",
"lint": "eslint core/**/*.js"
}, => "scripts": {
"test": "tap test/*_tests.js --reporter spec --coverage",
"pretest": "npm run lint",
"lint": "eslint core/**/*.js"
}, |
added coverage to test command part of resolving #622
I am going to close this as unneeded, considering the built in power tap has. as always, thanks for the thought and work you put into this Ben |
The changelog will reflect this conversation and credit you both for the discussion and work you put into this. Thanks https://github.com/pattern-lab/patternlab-node/wiki/ChangeLog |
I tested this on both the dev and dev-3.0 branch. I can make the pull request to either branch.
@bmuenzenmeyer @raphaelokon
Summary of changes: