# Heckle 1.1.0 Released

**URL:** <https://www.ruby-forum.com/t/heckle-1-1-0-released/79970>\
**Category:** Ruby\
**Created:** [December 20, 2006, 7:20pm UTC](https://www.ruby-forum.com/t/heckle-1-1-0-released/79970 "2006-12-20T19:20:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aguynamedryan](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/43a26b/32.png) [@aguynamedryan](https://www.ruby-forum.com/u/aguynamedryan)\
**Post date:** [December 20, 2006, 7:20pm UTC](https://www.ruby-forum.com/t/heckle-1-1-0-released/79970/1 "2006-12-20T19:20:43Z")

</div>

Heckle version 1.1.0 has been released!

[http://www.rubyforge.org/projects/seattlerb](http://www.rubyforge.org/projects/seattlerb)  
by Ryan D. and Kevin C.

Unit Testing Sadism.

From [http://glu.ttono.us/articles/2006/12/19/tormenting-your-tests-](http://glu.ttono.us/articles/2006/12/19/tormenting-your-tests-)  
with-heckle :  
Heckle is a mutation tester. It modifies your code and runs your  
tests to make sure they fail. The idea is that if code can be changed  
and your tests don’t notice, either that code isn’t being covered or  
it doesn’t do anything.

It’s a little weird, I know, but I like to think about it as pen-  
testing. It’s like hiring a white-hat hacker to try to break into  
your server and making sure you detect it. You learn the most by  
trying to break things and watching the outcome.

Anyway, Heckle was inspired by Jester, and Ryan D. wrote a proof  
of concept at RubyConf. As he notes, I went a little nuts and much of  
the current implementation I rewrote that night or on the plane home.

Changes:

== 1.1.0 / 2006-12-19

- 12 major enhancements: