We are evaluating user clover for its Test Optimization feature so that developers can run just the integration tests that are associated with their code changes. Integration tests, timewise, take up a large portion of the run time of our test suite, so it would be very useful to reduce the number that needs to be run.
At the moment Clover does not have direct support for test optimisation with the maven-failsafe-plugin. Shortly speaking, this is caused by a fact that the failsafe plugin does not fail tests during their execution but in a later build phase, so Clover does not "see" any exceptions thrown.
There is a workaround available, however. See this article:
Hi everyone, welcome to the kb articles for Opsgenie FAQs. I'm one of the Technical Support Engineers for Opsgenie who will be providing weekly posts on FAQs from customers. All alerts are ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.