Mock call assertions in PyTest - Framework Patterns

Framework Mode - Mock call assertions

Folder Structure

project-root/
├── tests/
│   ├── test_example.py
│   └── __init__.py
├── src/
│   ├── module.py
│   └── __init__.py
├── conftest.py
├── requirements.txt
└── pytest.ini
    

This structure keeps test files separate from source code. tests/ holds test scripts using mocks.

Test Framework Layers

• Test Layer: Contains test functions using unittest.mock to create mocks and assert calls.
• Source Layer: Contains application code to be tested.
• Fixtures/Helpers: conftest.py provides reusable mocks or setup code.
• Configuration: pytest.ini or environment variables to control test behavior.

Configuration Patterns

Use pytest.ini to configure pytest options like verbosity and markers.

[pytest]
addopts = -v --tb=short
    

Use conftest.py to define fixtures that provide mock objects or patching helpers.

Environment variables can control which mocks to enable or test modes.

Test Reporting and CI/CD Integration

pytest outputs clear pass/fail results with detailed tracebacks on failure.

Use plugins like pytest-html for HTML reports or pytest-cov for coverage reports.

Integrate pytest runs in CI/CD pipelines (GitHub Actions, Jenkins) to run tests on every commit.

Mock call assertion failures show which calls were expected vs. actual, helping debug test failures quickly.

Best Practices for Mock Call Assertions

• Use unittest.mock.Mock or patch to replace dependencies in tests.
• Assert calls with assert_called_once_with(), assert_any_call(), or assert_has_calls() for clear intent.
• Keep mocks focused on behavior, not implementation details, to avoid brittle tests.
• Use fixtures to create reusable mocks and reduce duplication.
• Clear mock call history between tests to avoid cross-test interference.

Self Check

Where in this folder structure would you add a new mock fixture to simulate a database call for multiple tests?

Key Result

Organize pytest tests with mocks in a dedicated tests folder, use fixtures for reusable mocks, and assert mock calls clearly for reliable test verification.