Many of the unit tests 'test' by printing out the output of some command. Instead they should use assert_equal to compare
the output to the expected (or at least the current) output.
Whenever you see messages and data appearing when you run the tests, it is an indication that the tests aren't complete
and are unable to detect errors in these commands.
Many of the unit tests 'test' by printing out the output of some command. Instead they should use assert_equal to compare
the output to the expected (or at least the current) output.
Whenever you see messages and data appearing when you run the tests, it is an indication that the tests aren't complete
and are unable to detect errors in these commands.
Originally reported on Rubyforge: http://rubyforge.org/tracker/index.php?func=detail&aid=1508&group_id=104&atid=1999
Improvement
Open
Minor
Many unit tests are incomplete