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

Replace Cobertura with JaCoCo #891

Merged
merged 1 commit into from Nov 8, 2019
Merged

Replace Cobertura with JaCoCo #891

merged 1 commit into from Nov 8, 2019

Conversation

ob-stripe
Copy link
Contributor

r? @brandur-stripe
cc @stripe/api-libraries

So I just noticed that our coverage reports have been broken for months, because we're using a lambda expression (here) and Cobertura doesn't support them (see cobertura/cobertura#274).

Given that the issue is 4 years old and still not fixed, I've followed the advice of someone in the thread and migrated from Cobertura to JaCoCo, another code coverage tool.

(Our coverage numbers are still fairly abysmal because ~nothing in com.stripe.param is tested, but that's a different story.)

Copy link
Contributor

@brandur-stripe brandur-stripe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, if they don't have lambda support by now, they may never have it. LGTM.

OOC: Given how definitive the previous failure was, I'm surprised that the build didn't exit with a bad status code and let us know. Do you know if that was a Cobertura-specific thing? Does Jacoco fix that problem?

@ob-stripe
Copy link
Contributor Author

My guess is that the Cobertura plugin crashed in a way that didn't cause Gradle to stop the execution, and a partial report was still produced and uploaded to coveralls.io by the Coveralls plugin. I'm not sure though -- it's definitely surprising that Gradle didn't stop and return an error.

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

Successfully merging this pull request may close these issues.

None yet

3 participants