-
Notifications
You must be signed in to change notification settings - Fork 43
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
Export coverage #194
Export coverage #194
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super!
@vweevers Please create some issues for this. |
Of course. I figured I'd wait for feedback first. |
I think before merging, I want to test this against memdown (and Sauce Labs). |
@vweevers Maybe we should take parts of this PR description and put into the README. WDYT? |
Sure, why not :) |
Hmm, unsure where to put the information. The |
Aah nevermind, some are linked already. |
See also #33 |
Adding it to the milestone. |
Opened issues:
|
Closes #162.
This disables coverage by default. If
--coverage
is passed, airtap collects code coverage per browser, written to.nyc-output/airtap-<hash>.json
in Istanbul 1.0 format. One can generate reports withnyc report
(nyc takes care of merging files from multiple browsers). In local mode, airtap writes to.nyc-output/airtap-local.json
(so that no cleanup is necessary between repeated runs, e.g. if you refresh the page).Usage in CI is
airtap --sauce-connect --loopback airtap.local --coverage test.js
, and if you want, add a Travis hook to post results to coveralls:Later we should:
.nyc-output
)nyc
)