$ rspec ~/insane-magic.spec
1) Rspec should not allow you to make shit up
Failure/Error: [1, 2, 3].should have(4).potatoes
expected 4 potatoes, got 3
Finished in 0.00042 seconds
1 example, 1 failure
# See the `potatoes` method call? Where the hell did that come from?
# Is it in rspec? It must be, surely. That's all I've required!
# [Goes off to grep the rspec gems for "potatoes"... doesn't find it]
# Hmmmm. Good for people new to testing you say? Really?
# The "choose your own method name and we'll ignore it" behaviour is
# not syntactic sugar, it's poison for people who are new to programming.
# It's a bloody daft idea to put it forward as good practice in a widely
# popular library.
# To be clear, `describe` and `it` I like. But you can stop there; there's
# just negative productivity to be had from there on in. The Contest gem adds
# support for these blocks to test/unit in 100 lines of code.