Andrew Grimm - Heckle: we break code! #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Heckle evaluates the thoroughness of your unit tests. It does this by making modifications to your production code, and seeing if those modifications cause any unit test failures. For example, it will turn ifs into unlesses, and replace strings and numbers with other strings and numbers or nil, or even delete lines of code! If no failures occur when your unit tests are run on the modified production code, then that code isn't being tested enough.
In this talk, I will discuss how Heckle has been useful to me in maintaining a one person Ruby project that's been worked on for three years, has 15K lines of production code, 11K lines of test code, and varying degrees of unit testing.