Author michael.foord
Recipients michael.foord
Date 2010-11-29.00:55:57
SpamBayes Score 1.61372e-05
Marked as misclassified No
Message-id <1290992159.72.0.107137027413.issue10573@psf.upfronthosting.co.za>
In-reply-to
Content
The unittest documentation, argument names and implementation need to be consistent about the order of (actual, expected) for TestCase.assert methods that take two arguments. 

This is particularly relevant for the methods that produce 'diffed' output on failure - as the order determines whether mismatched items are missing from the expected or additional to the expected.

The documentation, signatures and implementation of all two argument asserts need to be checked to ensure they are the same and implemented correctly.

Personally I prefer (actual, expected).
History
Date User Action Args
2010-11-29 00:55:59michael.foordsetrecipients: + michael.foord
2010-11-29 00:55:59michael.foordsetmessageid: <1290992159.72.0.107137027413.issue10573@psf.upfronthosting.co.za>
2010-11-29 00:55:57michael.foordlinkissue10573 messages
2010-11-29 00:55:57michael.foordcreate