1 expected but was 2is much more descriptive than
false is not true.
I agree with Bill and think it's a great guideline to follow when writing tests. Unfortunately, there are also times when I need to assert truth. These tests usually appear when I need to test a method that should return true or false. In these situations I've found it valuable to use
assertwhen programming in Ruby.
The largest reason for this choice is because Ruby treats everything that is not nil or false as true. Therefore, if you are testing the
coded?method and you have an implementation error such as:
def coded?Your test will still pass if the test is coded as:
state = :coded
def test_coded?However, this test will fail:
def test_coded?Clearly, you should also have a test that verifies that
assert_equal true, obj.coded?
coded?is false; thus, better coverage mitigates this risk. However, I still prefer the assert_equal test implementation because I feel it makes my test suite more robust.