-
Notifications
You must be signed in to change notification settings - Fork 178
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
Support a format compatible with codeclimate #119
Comments
👋 @blatyo, it's Ale from Code Climate. We have a new Unfortunately, I'm not an elixir expert. Do you think it would be possible to update Thanks! |
@ale7714 That's already supported with the https://github.com/parroty/excoveralls/blob/master/test/json_test.exs#L48 It's basically: {
"source_files": [
{
"name": "foo/bar.ex", // name of file
"source": "defmodule X\nend", // source of file
"coverage": [0, 1] // counts of coverage per line, where line is the index of the array
},
// other files
]
} If you can support that, there's basically nothing left to do. |
@blatyo great news! Thanks for pointing this out. Do you have a real example of the output of coverage for an elixir project? That would be helpful when work on adding the parser on our |
Does codeclimate/test-reporter#278 solve this issue? I would think that anything else actionable on this ticket could be covered by #104 |
Yep, this is solved |
Is #104 solved then? This only seems to address compatibility with codeclimate. |
I'm interested in pushing code coverage information to code climate, but the format of the output needs to be one of the ones they currently support. Would you be open to accepting a new output format for code climate?
I'm happy to do the work.
Thanks!
The text was updated successfully, but these errors were encountered: