A description of heckle and possible improvements.

2. University of New (South Wales)

3. @andrewjgrimm

4. http://andrewjgrimm.wordpress.com

6. Makes changes to production code- mutations

7. Your unit tests should fail when changes are made – killing mutants

9. Number of mutations proportional to size of codebase

10. Number of tests proportional to size of codebase

11. Therefore heckle time is ~ O(n^2)

13. Tells test/unit to stop running once each mutation has triggered a failing test

14. Should reduce running time

16. I've added a proc containing a request to throw a symbol

17. The calling of the test suite for a specific mutation occurs within a catch block

19. Random number seeding, to enable reproducible mutant creation

22. Or highlight particular portions vulnerable to mutation

23. Make available to other code metric software

26. Buster (from MythBusters)