Message85136
Patch for unittest on trunk.
It provides better default failure messages for assertTrue and
assertFalse (current is "AssertionError: None").
It also provides a new class attribute for TestCase: longMessage
This defaults to False. If set to True, passing in an explicit custom
message does *not* override the helpful default failure message in
asserts which tell you which objects were involved in the failure.
Even if set to True or False in a TestCase then longMessage can still be
overridden in individual tests by setting an instance attribute.
Needs docs.
Could longMessage default to True in 3.1. |
|
Date |
User |
Action |
Args |
2009-04-02 01:58:41 | michael.foord | set | recipients:
+ michael.foord |
2009-04-02 01:58:40 | michael.foord | set | messageid: <1238637520.24.0.827171540397.issue5663@psf.upfronthosting.co.za> |
2009-04-02 01:58:39 | michael.foord | link | issue5663 messages |
2009-04-02 01:58:37 | michael.foord | create | |
|