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

Branch coverage support for JaCoCo #108

Merged

Conversation

andrioli
Copy link
Contributor

You can follow the descriptions in the git commit history 😄

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 97.745% when pulling 4231f5c on andrioli:feature/branch-support-for-jacoco into 0a4b0e6 on trautonen:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 98.039% when pulling 31fa2f4 on andrioli:feature/branch-support-for-jacoco into 0a4b0e6 on trautonen:master.


// add branches. unfortunately, there is NO block number and
// branch number will NOT be unique between coverage changes.
int branchId = 0;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Probably is better to use an unique ID per source file or session instead of an unique ID per condition.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 98.039% when pulling 8f8bd97 on andrioli:feature/branch-support-for-jacoco into 0a4b0e6 on trautonen:master.

@jwgmeligmeyling
Copy link

jwgmeligmeyling commented Apr 1, 2019

Thanks for contributing this! I'm using this patch in my fork right now.

Question: to what extent is it conventional in Coveralls to identify branches by an index? Is a message like "Branches [[0, 14], [0, 15]] missed" the standard for all languages?

@amaembo
Copy link

amaembo commented Sep 3, 2019

@trautonen could you please merge this work and publish a new version? It's a pity that such a great PR is not merged for two years already. Thanks.

@PabloThiele PabloThiele merged commit dabaaa5 into trautonen:master Jun 21, 2023
@andrioli
Copy link
Contributor Author

Wow merged 6 years later, is this still working ?

If you guys need any help on this feel free to mention me :)

@jwgmeligmeyling
Copy link

Ive been using it 🤷🏻‍♂️

@PabloThiele
Copy link
Collaborator

Unfortunately, I still have no way to make the upgrade versions and push to Maven repo. I have no credentials and tooling for that. I'm wondering to create a new account there.. for the continuity of this project.

@jwgmeligmeyling
Copy link

I've been facing the same issue after taking over Querydsl 🤣

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 this pull request may close these issues.

None yet

5 participants