This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients lee yummy, serhiy.storchaka, steven.daprano, zach.ware
Date 2020-05-25.20:31:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1590438694.21.0.55430685837.issue40761@roundup.psfhosted.org>
In-reply-to
Content
`unittest.TestCase.assertTrue` is simple enough (the entire implementation is copied below) that there is almost no way for it to fail to raise some kind of exception when its first argument is not truthy:

    def assertTrue(self, expr, msg=None):
        """Check that the expression is true."""
        if not expr:
            msg = self._formatMessage(msg, "%s is not true" % safe_repr(expr))
            raise self.failureException(msg)

This basically hasn't changed in the 19 years since the unittest module was added (though variously at times named `assert_` or `failUnless`), so I'm going to go ahead and close the issue.
History
Date User Action Args
2020-05-25 20:31:34zach.waresetrecipients: + zach.ware, steven.daprano, serhiy.storchaka, lee yummy
2020-05-25 20:31:34zach.waresetmessageid: <1590438694.21.0.55430685837.issue40761@roundup.psfhosted.org>
2020-05-25 20:31:34zach.warelinkissue40761 messages
2020-05-25 20:31:34zach.warecreate