The common causes of tests failing at the coverage stage are PIT picking up tests not included/are excluded in the normal test config Tests rely on an environment variable or other property set in the test config, but not set in the pitest config Tests have a hidden order dependency that is not revealed during … Read more
There is also PIT which can be hooked into your build via a maven plugin or command line interface. It provides much nicer reports than the other available tools with combined mutation and line coverage. It also runs considerably faster than the source based tools for Java such as Jester, and about twice as fast … Read more
A brief search resulted in: PlexTest: http://www.itregister.com.au/products/plextest_detail.htm Insure++: http://www.parasoft.com/jsp/products/insure.jsp;jsessionid=baacpvbaDywLID?itemId=63 MILU (may be only for C): http://www.dcs.kcl.ac.uk/pg/jiayue/milu/ With that said, you need to realize that mutation testing isn’t particularly useful (at least from some stuff I’ve previously read). It’s an interesting tool when faced with hard (metaphorically speaking) asserts and for making sure that data requirements … Read more
The usefulness of unit tests is no longer discussed. They are essential in conception of a quality application. But, how can we assess their relevance? A code coverage indicator up to 100% doesn’t mean the code is 100% tested. This is just a view of executed code during unit tests execution. Mutation testing will allow … Read more