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 coverage to CI; use a coverage service #2620

Closed
boneskull opened this issue Dec 2, 2016 · 2 comments · Fixed by #2672
Closed

add coverage to CI; use a coverage service #2620

boneskull opened this issue Dec 2, 2016 · 2 comments · Fixed by #2672

Comments

@boneskull
Copy link
Contributor

nyc is appropriate for Node.js coverage with all the process forking we need to do; karma-coverage probably fine for browser.

Coveralls.io is straightforward. Code Climate is probably going to have more info. Codacy is another one. There are a ton of these things. Anybody have a favorite?

@boneskull boneskull added the qa label Dec 2, 2016
@pgoldrbx
Copy link

pgoldrbx commented Jan 16, 2017

+1 for nyc and karma-coverage (though combining the output might still have some issues due to file paths in karma)

From experience, Coveralls is nice in that you'll get per-branch/PR coverage information, versus Code Climate which currently only shows reports on the default branch. I have no experience with Codacy. It might not matter too much which you choose to start as anything is better than nothing, but being able to identify coverage changes on PRs is a pretty important OSS concern.

Code Climate does offer a fantastic environment for static analysis, though. Duplication and complexity detection are really good there. You can use these tools together, of course.

edited for typo

@coderbyheart
Copy link
Contributor

Seems like a duplicate of #2351

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 a pull request may close this issue.

3 participants