scenario-testing

End-to-end scenario tests execute real services and data by writing scenarios in a .scratch/ directory. This approach enforces no mocks, ensuring integration issues surface during feature validation across local, CI, or staging environments.

Recurring end-to-end test patterns are extracted and documented in a scenarios.jsonl file. This creates reusable specifications, allowing development and QA teams to consistently validate code changes independently.

Yes, scenarios are designed to run standalone in CI/CD pipelines. They execute against actual dependencies without mocks, validating features across local, CI, or staging environments while keeping scratch environments out of version control.

Real dependencies avoid the integration issues that mocks can mask. By executing end-to-end scenarios with actual services and data, developers validate code changes against true system behavior rather than simulated responses.

Yes, scenario tests require a .scratch/ directory to write and manage tests exercising real systems. This directory must remain ignored by version control while scenarios run independently across environments.

Real end-to-end testing requires actual services and data, demanding the ability to run scenarios independently across local, CI, or staging environments. It may not suit contexts lacking real service access or standalone execution capabilities.