Runbook 07 — Custom fixtures + composition

This preview outlines the capability introduced by this runbook and the role it plays in the larger automation system.

What this runbook does

Test systems fail when setup is distributed across tests. This runbook centralizes execution into a single fixture layer that defines authentication, environment targeting, and domain access under a controlled, deterministic contract.

• Fixture layer owns auth, API clients, and domain primitives
• Tests receive dependencies as inputs, with no ad hoc setup or construction
• Execution modes are defined at the project level instead of hidden in test logic

What it proves

Execution becomes a controlled system boundary—enabling reliable scaling, reuse, and downstream automation.

Access

The full runbook includes fixture contracts, auth ownership patterns, project routing, and composition rules used to keep execution deterministic.