# Failed: assert False, 'Custom failure message'

- **ID:** `python/pytest-fail-with-traceback`
- **Domain:** python
- **Category:** runtime_error
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

A test uses `pytest.fail('Custom failure message')` or `assert False` to deliberately fail, often for debugging or conditional failure logic.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| 3.8 | active | — | — |
| 3.9 | active | — | — |
| 3.10 | active | — | — |
| 3.11 | active | — | — |
| 3.12 | active | — | — |

## Workarounds

1. **** (90% success)
   ```
   Use pytest.skip() instead if the test is not yet ready: `pytest.skip('Test not implemented')`
   ```
2. **** (95% success)
   ```
   Implement the missing logic and remove the fail statement.
   ```

## Dead Ends

- **** — The fail might be intentional to indicate an unimplemented test; removing it hides the gap. (70% fail)
- **** — This turns a failing test into a passing one, which can mask real issues. (90% fail)