Message270278
In looking at the source for unittest.TestCase I was very surprised to see quite a few assertion methods that are not included in the module documentation. Every available assertion method should be included in the library documentation. Users should not have to look at the source to see what's available — in fact, why would it even occur to the typical user to do that?
Also, I think the phrase "provides several assert methods to check for and report failures" is an understatement — it provides MANY assert methods.
I think "assertion method" is a better term than "assert method". |
|
Date |
User |
Action |
Args |
2016-07-13 00:40:21 | MLModel | set | recipients:
+ MLModel, docs@python |
2016-07-13 00:40:21 | MLModel | set | messageid: <1468370421.07.0.622363937754.issue27504@psf.upfronthosting.co.za> |
2016-07-13 00:40:20 | MLModel | link | issue27504 messages |
2016-07-13 00:40:18 | MLModel | create | |
|