What problem does it solve? Python test suites often become inconsistent and unmaintainable when each developer follows different conventions for structure, naming, and assertions. This Skill enforces a single mandatory testing standard so every test follows the same AAA pattern, naming scheme, and verification rules. ## Core Features & Use Cases - AAA Pattern Enforcement: Every test must separate Arrange, Act, and Assert phases with explicit comments, with no combined Act & Assert blocks or try/finally cleanup. - Strict Naming and Structure: Tests must use the Should_{ExpectedBehavior}When{Condition} format, mirror the production code hierarchy, and use sut/actual/expected variable names. - Mocking and Test Data Rules: All mocks must be verified, and test data should be created with Mother or Builder patterns (polyfactory-based), with async support via pytest-asyncio. - Use Case: When writing unit, integration, or acceptance tests for a Python service, activate this Skill so the AI generates tests that pass code review on the first attempt. ## Quick Start Write unit tests for my Python service class following the mandatory AAA pattern and Should_When naming conventions.