Exception testing

Ensures code under test raises the correct exception type with the expected error message

Input validation: verifying that malformed or out-of-range inputs raise ValueError with a descriptive message; API contract testing: confirming that precondition violations surface as specific exception types; Error path coverage: asserting that failure modes produce distinguishable exceptions rather than silent failures

pytest test suites, Python unit testing, CI/CD pipelines, TDD workflows

with pytest.raises(exception_type, match=pattern): callable_under_test(*args, **kwargs)

with pytest.raises(..., match=...): ...

exception_type: exception class such as ValueError or TypeError, pattern: regex string matching the exception message

• pytest.fixture
• pytest.mark.parametrize
• assert
• pytest.warns
• pytest.deprecated_call

• unittest.TestCase.assertRaises: callback style instead of context manager
• less readable for multi-line code
• try/except with pytest.fail: manual and verbose
• pytest.raises is the idiomatic replacement
• pytest.raises without match: verifies exception type only but misses message validation

Placing code before the with block instead of inside it — the exception must be raised within the context manager body or the test fails Using match with a plain string containing regex special characters like parentheses or dots — match uses re.search so these are interpreted as regex, causing false failures Expecting pytest.raises to catch exceptions from code that runs after the with block exits — only code inside the indented block is monitored Forgetting the colon after the with statement — syntax error that prevents the test from running

unittest.assertRaises: callback-based API with no regex match support, pytest.raises is more Pythonic; try/except/pytest.fail: manual exception checking, more verbose and error-prone; pytest.warns: analogous pattern for warning assertions instead of exceptions

Coming from unittest: may write self.assertRaises(ValueError, func, arg) — pytest uses a context manager, not a callback; Coming from Java/JUnit: may expect @Test(expected=...) annotation — pytest has no decorator equivalent, use the with statement instead; Coming from JavaScript/Jest: may expect expect(() => fn()).toThrow() — pytest requires the with context manager form

• pytest.raises
• pytest.warns
• pytest.deprecated_call
• pytest.fixture
• assert

Do not use pytest.raises for exceptions you do not actually care about testing — if any exception is acceptable, the test is too permissive. The match parameter uses re.search not exact string equality, so partial matches pass; use ^ and $ anchors for exact matching. If the code inside the with block raises a different exception type than expected, the test fails with a detailed diff showing the actual exception.

Catches regressions where error handling is accidentally removed or exception types are changed, and ensures error messages remain meaningful for debugging and user-facing diagnostics.

Like a safety net that only catches one specific type of falling object — if the wrong thing falls, the net breaks and the test fails loudly.

The match parameter was added in pytest 2.8. Prior to that, you had to manually inspect exc_info.value.args[0]. The as exc_info syntax allows post-assertion inspection of the caught exception object.

pytest.raises with exc_info for multi-assertion exception validation; pytest.mark.parametrize for testing multiple exception-triggering inputs