The trouble with RSpec is that you, and your team, must to some degree own the complexity built into the framework. If that's something that you're comfortable

The trouble with RSpec is that you, and your team, must to some degree own the complexity built into the framework. If that's something that you're comfortable with, the complexity pays you back in spades for the literacy that it provides your tests. I'm strongly in favor of written documentation for gems that you assume others will consume. But if you're writing app code and the primary consumers of it are the other programmers on your project, literate tests really, really help. RSpec, and its 80%-as-nice-but-much-simpler cousin, Shoulda, are your friend here.