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:
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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