wired-runner-fixture

You can reduce boilerplate by extracting a shared wired pytest fixture that centralizes object construction and mocking. This fixture initializes common dependencies and state upfront, allowing test methods to focus on behavior verification rather than repetitive setup configuration.

A wired pytest fixture provides a pre-configured setup for E2E tests by initializing common dependencies and state in one place. It is used to eliminate repetitive fixture construction and patching across multiple test methods that need to construct the same object with heavy dependencies.

Centralize fixture creation by applying a shared wired fixture that initializes the E2ERunner and its dependencies. This enables safe patching by isolating the setup logic in a single location, allowing all test methods to reference the pre-configured object without duplicating mock configurations.

Yes, you can refactor test setup behavior in one place by using a centralized wired fixture. Swapping fixture behavior in a single location automatically propagates changes across all tests that reference it, eliminating the need to update repetitive setup code in individual test methods.

Yes, this fixture approach specifically applies to test classes where multiple methods construct the same object with heavy dependencies. It centralizes the wiring of the E2ERunner across tests for consistency, ensuring each method receives a pre-configured instance without duplicating construction logic.

A shared wired fixture centralizes setup but may introduce state leakage between tests if not properly isolated. It is best suited for test classes needing consistent dependency mocking, but tests requiring unique object configurations or independent state may not benefit from this centralized approach.