Fix true? errors in specs by being more specific

`be_true` fails recently (maybe because Rspec3 is out, I don't actually know) because it calls `true?`, which is not a valid method for quite a few classes (at least in Ruby 1.9.3).

This PR fixes it by not using `be_true` and being more specific instead.