Link Details

Software testing aims at checking the correctness of a program. But how can you check the correctness of your tests? Quis custodiet ipsos custodes? Mutation analysis can help you evaluate the quality of a test suite.

Posted by Michael_MULLER  |   Nov 12 2012 / 16:13

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.


User 771987 avatar

Steve Mcduff replied ago:

Looks oddly similar to Jester

Reply 0 votes
User 461284 avatar

hjc replied ago:

Reply 1 votes
User 1082197 avatar

alightgoesout replied ago:

As mentioned by Steve Mcduff, Jester is indeed another mutation testing tool for Java. PIT offers several improvements. For instance, PIT does in-memory bytecode mutation. This is more efficient than Jester, which mutates the java source and actually writes it to disk before executing it. Also PIT is still supported and developed whereas Jester has not been actively developed for years. As pointed by hjc, the PIT website hosts a detailed comparison with other mutation testing frameworks.

Reply 0 votes
User 771987 avatar

Steve Mcduff replied ago:

Great, good to know. The best use I found for Jester (and now potentially PIT) was to run unit test education sessions. Ask participants to create unit tests for a class, and then show them how good or bad their tests are with a few mutations. It's a struggle to encourage good basic unit test practices in most organizations. I feel levels usually go from 0 - no UT 1 - basic UT 2 - good UT using code coverage to find gaps 3 - use mutation testing #3 is probably a bit to costly to implement consistently on large projects, but if someone can prove me wrong, I'm very interested in learning how.

Reply 0 votes

Recommended Links

Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone