I have instrumented my web app (a Maven project) source code (NOT tests) using clover and deployed it to tomcat (Initstring=absolute path & flushpolicy = threaded, distributed cov =ON). This acts as a clover client.
Now, i have a different project created for my integration tests (an Eclipse project) and instrumented where coverage.db is pointed to a different location (flushpolicy = threaded, distributed coverage=ON). This acts as a clover server. When i run my "Junit" tests, i was able to see the code coverage but not per-test coverage.
I understand that the clover server & client are using different Initstring values. What should be done to get per-test coverage? Merging dbs?
You should build both application and tests using the same database. You shall not merge databases - a merged database can be used for reporting only.
In case you'd need to change initstring value at runtime, you can use the -Dclover.inistring=/path/to/clover.db property.
I am seeing different. When i built project A from eclipse it created clover.db of size ~1MB and when i built project B from eclipse (initstring is same), it didn't update the file instead it overwrote existing clover.db (new size is ~500KB). I am using clover version #3.2.2. Is there something that i am missing here?
Yes, I was building my projects from Eclipse IDE. Now, i switched my "dev" project to maven while my "test" project remains to be the Eclipse project.
Followed steps as below to get per-test coverage:
1. First, i instrumented my "test" project using Eclipse IDE => this has generated clover.db file
2. Next, i instrumented my "dev" project using maven => this has updated my existing clover.db bcz my initstring is same and built a war out of it which is inclusive of all my instrumented classes (does not include "test" files).
3. Deployed war to tomcat container (also, distributed coverage ON)
4. Now i executed a JUnit test (distributed coverage ON and communicating to my tomcat client) => generated new coverage files as expected but i could not get per-test coverage.
Something else that i should be doing to achive per-test coverage?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...
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