Assertion

Verifies that a condition evaluates to True, failing the test if it does not.

Unit testing: verifying a function returns a truthy value; Unit testing: checking that a flag or state variable indicates success; Unit testing: confirming a collection is non-empty or an object is not None.

Python unittest.TestCase subclasses, pytest-based test suites using unittest compatibility, Django test cases.

self.assertTrue(condition)

self.assertTrue(condition)

condition: any expression that evaluates to a boolean or truthy value.

• self assertTrue True False assertFalse assertEqual assertIsNotNone

• assertFalse(condition) assertTrue(not condition) assertTrue(len(seq) > 0) assertTrue(isinstance(obj
• cls))

Using plain assert instead of self.assertTrue — plain assert can be silently disabled with -O flag, causing tests to pass when they should fail. Passing a non-boolean without intent — relies on Python truthiness and can mask logic errors where assertEqual or assertIs would be clearer. Confusing assertTrue with assertEqual — assertTrue(1 == 2) gives a useless failure message, while assertEqual(1, 2) shows both values. Omitting self. prefix — causes NameError because assertTrue is a method on the TestCase instance.

assertFalse: asserts the condition is False assertEqual: asserts two values are equal assertIs: asserts object identity assertGreater: asserts a numeric comparison

Coming from JavaScript/Jest: may write assertTrue(condition) as a bare function call — Python requires self.assertTrue() inside a TestCase method. Coming from pytest: may write assert condition instead of self.assertTrue(condition) — pytest rewrites bare asserts for better messages, but unittest requires the method call.

• unittest_assertions

Do not use assertTrue when a more specific assertion (assertEqual, assertIsNotNone, assertIn) communicates intent better and provides clearer failure messages. No measurable performance impact; assertion overhead is negligible compared to the code under test. Non-obvious: assertTrue(None) and assertTrue(0) fail, while assertTrue([]) and assertTrue('') also fail — any falsy value triggers failure, not just False.

Signals the test author’s expectation that the condition should hold; a failure indicates a defect in the code under test.

Think ‘assert true’ when you need to verify a condition holds.

Part of the unittest.TestCase assertion API; provides a clear failure message showing the offending value.

Consider using assertTrue with a custom message for clearer failure reports, or replace with more specific assertions like assertGreater or assertIsInstance when appropriate.