Comment Comment by colonwqbang I always found it a bit useless to be fussing over phrasing like this. What does it matter if we call itexpect(x).to(equal(y))orx.should_be(y)orassert_eq(x, y)These are just different ways of saying the same thing. The first two aren't really better than the last at conveying what's going on.Although I like Ruby and Rspec, this desire for "beautiful code" and "making the code read like English" never rhymed with me. parent colonwqbang 5 years ago
expect(x).to(equal(y))
or
x.should_be(y)
or
assert_eq(x, y)
These are just different ways of saying the same thing. The first two aren't really better than the last at conveying what's going on.
Although I like Ruby and Rspec, this desire for "beautiful code" and "making the code read like English" never rhymed with me.