$npx skillfedfor your agent

Pytest Mocking Strategy

Learn a decision-driven framework for mocking in pytest that separates external boundaries from business logic. This skill covers autospec enforcement, async mock patterns, reusable mock factories, and a clear matrix for what to mock versus what to test directly. Master the golden rule—mock external dependencies, test the unit in isolation—to write tests that survive refactoring.

Pytest Mocking Strategy teaches when and how to mock dependencies in unit tests, covering autospec, AsyncMock, and what should never be mocked.

AI-generated summary based on this skill's SKILL.md

1 0 unlicensed, metadata onlyupdated by dawiddutoit

Decision gist · record as of 2026-01-26

Pytest Mocking Strategy teaches when and how to mock dependencies in unit tests, covering autospec, AsyncMock, and what should never be mocked. Learn a decision-driven framework for mocking in pytest that separates external boundaries from business logic. This skill covers autospec enforcement, async mock patterns, reusable mock factories, and a clear matrix for what to mock versus what to test directly. Master the golden rule—mock external dependencies, test the unit in isolation—to write tests that survive refactoring.

manual: git clone https://github.com/dawiddutoit/custom-claude → cp -r custom-claude ~/.claude/skills/pytest-mocking-strategy

Use it when

  • Pytest Mocking Strategy covers best practices for mocking that center on isolating dependencies during testing.
  • Pytest Mocking Strategy outlines best practices including autospec enforcement to prevent interface drift.
Same gist for agents: .md · .json

Install

dawiddutoit/custom-claude/pytest-mocking-strategy · repository language: Python

generated, unverified - the skill's exact subdirectory could not be determined; check the repository on GitHub

Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

What mocking strategies should I use in pytest?

Pytest Mocking Strategy teaches a decision-driven framework that separates external boundaries from business logic. The core approach: mock external dependencies, test the unit in isolation. Key strategies include using autospec enforcement to catch interface changes, async mock patterns for concurrent code, and reusable mock factories to reduce duplication. This golden rule ensures your tests survive refactoring by validating behavior without coupling to implementation details.

How do I mock in pytest effectively?

Pytest Mocking Strategy covers best practices for mocking that center on isolating dependencies during testing. Use autospec to enforce mock contracts, apply async mock patterns when testing concurrent operations, and build reusable mock factories for consistency. The skill emphasizes a clear matrix for what to mock versus what to test directly—mock external boundaries (APIs, databases, file systems) while testing your business logic in isolation.

What are pytest mock best practices?

Pytest Mocking Strategy outlines best practices including autospec enforcement to prevent interface drift, async mock patterns for modern async code, and mock fixtures for reusable test doubles. The framework prioritizes mocking external dependencies while testing core logic directly. This approach ensures tests remain maintainable, catch real integration issues, and don't break when internal implementation changes.

How do I implement effective test doubles and mock objects?

Pytest Mocking Strategy teaches you to implement test doubles through reusable mock factories and a structured decision matrix. Use autospec to create mocks that enforce the real interface, apply async mock patterns for concurrent scenarios, and organize mock setup in fixtures. This skill ensures your mock objects accurately represent dependencies without becoming brittle or overly complex.

How do I isolate dependencies during pytest testing?

Pytest Mocking Strategy provides patterns for isolating dependencies by mocking external boundaries—APIs, databases, file systems—while keeping your unit logic under test. Use mock fixtures for reusable test doubles, autospec to enforce contracts, and async mock patterns for concurrent code. This isolation ensures your tests validate business logic independently and catch real integration issues separately.

What is the difference between pytest monkeypatch and mock?

Pytest Mocking Strategy covers both tools within its framework. Monkeypatch is lighter-weight and ideal for simple replacements in the same process; mock (via unittest.mock) is more powerful for creating sophisticated test doubles with call tracking and autospec enforcement. The skill teaches when to use each: monkeypatch for quick local patches, mock for complex external dependency isolation and contract validation.

Let your AI agent find skills like this

Example. Real query, live index.

You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.

wish › “Learn mocking strategies and patterns for pytest unit tests”

Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →

Related skills

Pytest Application Layer Testing
by dawiddutoit · dawiddutoit/custom-claude

This skill teaches pytest patterns for testing application layer code—use cases, services, and data transfer objects—with mocked external dependencies at layer boundaries. Learn to structure tests with fixtures, verify orchestration behavior, and validate error handling and recovery logic.

no license declared → metadata onlyupdated Jan 2026
★ 1repo stars
Pytest Type Safety
by dawiddutoit · dawiddutoit/custom-claude

Add type annotations to test functions and fixtures, then configure mypy to validate them during test runs. Use create_autospec for type-safe mocks that enforce interface contracts and catch typos at runtime.

no license declared → metadata onlyupdated Jan 2026
★ 1repo stars
Pytest Adapter Integration Testing
by dawiddutoit · dawiddutoit/custom-claude

Master testing strategies for adapters connecting to external systems. Learn when to mock HTTP responses with aioresponses, spin up real services with testcontainers, and handle error paths in Kafka and other integrations.

no license declared → metadata onlyupdated Jan 2026
★ 1repo stars
Pytest Configuration
by dawiddutoit · dawiddutoit/custom-claude

Set up pytest with production-ready configuration patterns covering test discovery, async support, custom markers, and coverage reporting. Includes conftest.py hierarchy examples and fixture scoping strategies for consistent test behavior across environments.

no license declared → metadata onlyupdated Jan 2026
★ 1repo stars
Pytest Test Data Factories
by dawiddutoit · dawiddutoit/custom-claude

This skill teaches patterns for building maintainable test data in pytest through factory functions, builder patterns, and fixture factories. Learn to eliminate test data duplication by providing sensible defaults and easy customization for domain objects, complex structures, and parameterized datasets.

no license declared → metadata onlyupdated Jan 2026
★ 1repo stars
Pytest Async Testing
by dawiddutoit · dawiddutoit/custom-claude

Master async testing in Python with production-ready patterns for pytest-asyncio, async fixtures, and mocking. Covers FastAPI endpoints, Kafka clients, context managers, and async generators with proper event loop isolation.

no license declared → metadata onlyupdated Jan 2026
★ 1repo stars

More skills Util Resolve Serviceresult Errors (unlicensed) · Test Setup Async (unlicensed) · Pytest Domain Model Testing (unlicensed) · Textual Test Fixtures (unlicensed) · pytest (MIT) · Pytest Coder (NOASSERTION) · python-testing (MIT)

Tags
test-doublesunit-testingmock-patternstest-fixturesdependency-isolationpytest-pluginstesting-methodologycode-quality