In my case, I have to get code coverage in server.For that I use clover. I have executed test cases for some scenarios through client side manually (That means logging to the web application and manually test some scenarios ). Then I want to get result as what is the test coverage during testing. While I test, there may be situation like application build again. That means I lost my coverage data file. After testing finish, then it shows only coverage which is covered after new app build. Clover provides history point option which save .xml.gz file on the history directory. I want to know How I integrate this history file and currently updated clove.db file and create a report which cover all of my testing ? ( Before start build i can executed ant target for save history point and save the current coverage result)
Hi, you can't simply merge current clover.db and coverage files with Clover history point. However you can generate Clover reports (current and historic one) linked together.
Please take a look at current and historical elements of the clover-report documentation
Then I want to get result as what is the test coverage during testing. While I test, there may be situation like application build again. That means I lost my coverage data file.
Could you please clarify what would you like to achieve exactly?
Please note that if application has been rebuilt, then your all previous manual tests are no longer valid as you never know how source code changed. So for this reason I don't see a value of keeping outdated coverage data as well.
Unless you have different intent?
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs