I'm trying to build a test bed for our Integration Tests such that we can deploy a Clover-built version of a service and run various integration tests on it, shut it down, and then generate a report.
In theory, this works. But, Clover is insisting that the clover.db be in the path that it was for the built binary. Additionally, it wants to have access to that same exact directory to write the clover runtime files (makes sense, I guess).
We could hack this up (since all of our services follow the same pattern), but it breaks the encapsulation paradigm of having the clover.db and clover output managed with the service installation.
But, otherwise, looks like this solution is going to work for us.
Thanks for any help - Howie
You can use:
As well as change where clover.db is produced during code compilation:
Happy New Year! We hope you all had a safe and restful holiday season. 2020 was a unique year full of unforeseen events; however, as we enter the new year of 2021, we’re optimistic for the light at t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events