e2e-tests

Real-service end-to-end testing governance standardizes test creation and review to verify complete user workflows against live APIs and data, strictly prohibiting mocks to ensure verifiable outcomes.

You run end-to-end tests without mocks by executing the repository's standard justfile recipe, which validates full user journeys against live services and real data environments.

You should avoid mock services in E2E testing because mocks bypass real systems and data, whereas prohibiting mocks ensures tests exercise actual APIs to produce verifiable end-to-end outcomes.

No, this E2E testing approach explicitly avoids unit and integration tests within the repository, enforcing exclusive reliance on end-to-end tests to validate full user-facing workflows from start to finish.

You prevent flaky runs in end-to-end testing by applying consistent test organization, naming conventions, and environment isolation, guided by context-driven Next Actions defined in central context files.

You should not use real-service E2E tests for isolated component validation or internal logic checks, as this governance model focuses strictly on complete user-facing workflows rather than granular unit testing.