-
Notifications
You must be signed in to change notification settings - Fork 606
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
Collect code coverage data #463
Comments
... or perhaps not so simple. See https://github.com/danielmlipton/travis-ci-js-test-driver |
The easiest way to get this might be to port our tests to Mocha or QUnit. We should probably do this anyway, it looks like js-test-driver has stagnated (no releases in >2 years). |
I followed the jstd coverage instructions and got some basic numbers. Generally coverage is pretty high! I'll see if I can generate an HTML report.
|
And here's a nicer view on coveralls.io. Overall code coverage is ~87%. Some areas that are really lacking testing include:
This also brings up a lot of IE checks that we missed! |
blanket.js and coveralls.io are a killer combo. We've done the hard work of writing the unit tests, let's get the payoff!
The text was updated successfully, but these errors were encountered: