solnic/virtus — pull request #133 by mattgillooly (2012-12-02 22:19:49+00:00)
Title: use equal instead of be for boolean coercion specs

While investigating an open issue[1], I found myself wondering if the
`be(true)` and `be(false)` assertions were actually checking that we had
the explicit `true` and `false` values we wanted, versus just checking
Ruby truthiness, as in RSpec's `be_true` and `be_false`

In fact, the assertions do assert equality with `true` and `false`, and
this pull request does not change the behavior of the tests at all. I
simply think using `equal` makes the behavior more obvious.

[1] https://github.com/solnic/virtus/issues/132