assert_equal arguments are backward

[dchelimsky]

In test/unit, minitest, junit, etc, the arguments are actual, expected. This allows you to read "assert_equal foo, bar" as "assert_equal_foo bar".

Ironically, that people often screw up the order of these arguments was one of the initial motivations for "actual.should eq(expected)". FWIW. From one grump to another ;)

[hopsoft]

Thanks for the heads up. I'll swap them.

[dchelimsky]

Cool. Also - I don't know if you know this but RSpec will let you use asserts like this:

RSpec.configure {|c| c.expect_with :stdlib}

That pulls in the assertions from test/unit in Ruby < 1.9, and MiniTest in Ruby >= 1.9. Won't give you RSpec's failure messaging, but that's how most folks are handling this these days.

[hopsoft]

I wasn' t aware they were still supporting this. GrumpyOldMan preserves the nice RSpec error formatting.

The arg order has been fixed.