Skip to content
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

Add test:coverage npm script to check coverage locally #891

Merged
merged 2 commits into from
Jan 14, 2019

Conversation

ScottRudiger
Copy link
Contributor

Currently, there is no standard way to check coverage locally.

From the README:

Run npm run test:coverage to run the test suite with coverage report.

This PR simply adds a test:coverage npm script that checks coverage via nyc.

Happy to change up the script if there's a different variation you'd like to run. Alternatively, we could remove the above line from the README instead of adding a script.

@ScottRudiger
Copy link
Contributor Author

I just noticed there's also the ci:test script, which does almost the same thing.

Should we add the test:coverage script anyway to remain consistent with the README and as a distinction between development & CI?

@luisrudge luisrudge merged commit 14656e3 into auth0:master Jan 14, 2019
luisrudge added a commit that referenced this pull request Jan 21, 2019
luisrudge added a commit that referenced this pull request Jan 21, 2019
* Revert "Add `test:coverage` npm script to check coverage locally (#891)"

This reverts commit 14656e3.

* Revert "Update vulnerable dependencies (#892)"

This reverts commit 8381e4b.

* Revert "Release 9.9.0 (#890)"

This reverts commit 535484f.

* Revert "Don't use storage when inside the UNiversal Login Page (#889)"

This reverts commit 9b2a98f.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants