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

Clover Merge of DB #142

Open
arieskeds opened this issue Apr 8, 2021 · 1 comment
Open

Clover Merge of DB #142

arieskeds opened this issue Apr 8, 2021 · 1 comment

Comments

@arieskeds
Copy link

Hello Clover Team,

I am using Openclover to track the code coverage of my java web application. As part of my daily deployments, I create a new DB and keep the old generated DB in my archive. At the end of the month I tried to merge all the clover DBs to get a consolidated report out of the merge DB to track how much code was executed and what is left to be covered.
While doing this activity in march I had a class A which has about 50% code coverage and now in April when I try to merge the DB, I see no coverage for that class A. Ideally, as an outcome of this merge, Class A should have at least 50% coverage.

Did anyone come across this issue earlier that coverage b/w 2 DBs can lose during merge.
Additionally, if my Java file is changing within this time, will this cause a problem in merging.
Also, say in march for Class A i had covered 50% execution and in April i did covered additional 30%, will merge give me 80% or 50% or 30%, assuming the class was never changed.
What happens in above situation if the class has changed ?

@arieskeds
Copy link
Author

Hi Clover Team,

Please let me know if anyone can advise about above mentioned issues.

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

No branches or pull requests

1 participant