Verifies that the executed code produced no error messages in its log output, serving as a test oracle for correctness.

Expresses the expectation that the code under test runs without generating any log entries containing the word 'error'.

Used after executing a function or test case where the expected behavior is to produce no error logs; common in unit tests, integration tests, and CI pipelines that capture log output.

Unit testing frameworks, test suites, continuous integration pipelines, debugging sessions where log output is captured and inspected for absence of error tokens.

assert substring not in log_output

assert ... not in ...

substring: str, log_output: str

• error
• log
• output
• assert
• not in
• string
• substring
• captured
• logs
• stderr

• "error" -> 'warning'
• 'fail'
• 'exception'
• 'traceback'
• log_output -> output
• logs
• captured_log
• stderr

Using 'in' instead of 'not in', misspelling the variable name, case‑sensitivity mismatches, relying on assert which can be disabled with Python -O flag, confusing substring check with exact error message match.

"assert 'error' in log_output" (expecting an error), "assert 'error' not in log_output.lower()" (case‑insensitive), "unittest.assertNotIn('error', log_output)" , "if 'error' in log_output: raise AssertionError\).

Coming from C/Java: may expect assert to always execute at runtime → Python's assert is stripped with -O flag; use unittest or pytest assertions for guaranteed checks.

• assertion statements
• membership tests
• log‑validation patterns

(1) Do not use for critical runtime validation in production since assert is disabled with -O. (2) Substring search is O(n) on log length; negligible for typical test logs but avoid on very large outputs. (3) Case-sensitive: 'Error' or 'ERROR' will pass undetected; use .lower() if case-insensitivity is needed.

Provides a lightweight smoke test that catches regressions where error messages appear in logs, preventing silent failures from reaching production.

Like a bouncer checking that 'error' isn't on the guest list — if it shows up in the log, something went wrong.

Assert statements can be disabled when Python is executed with the -O optimization flag, so they should not be relied upon for critical runtime checks in production.

Replace raw assert with a dedicated testing assertion such as unittest.TestCase.assertNotIn or pytest's assert 'error' not in caplog.text for more robust, non-optimizable checks.