ballroom-flow-validation-and-qa

To validate end-to-end test routines in Weave Steps, use a runbook covering harness conventions, layer ownership, and TDD discipline. It ensures robustness by applying RED→GREEN→REFACTOR practices across domain, worker, component, contract, and E2E layers.

Testing layer responsibilities in Weave Steps QA divide ownership across domain, worker, component, contract, and E2E layers. Clarifying these boundaries ensures correct test distribution, harness convention adherence, and targeted coverage management for each architectural layer.

Manage test coverage thresholds by applying a ratchet plan that prevents coverage regression, and maintain TEST-MAP.md by updating the feature-test mapping document. This ensures continuous code quality tracking and accurate test validation across the project.

Yes, you can use vitest and Playwright for Weave Steps test validation. The validation process requires knowledge of these testing frameworks to execute TDD discipline, enforce harness conventions, and validate routines across the different testing layers.

The best way to add tests at each Weave Steps testing layer is by following provided step-by-step recipes. These instructions detail adding tests for domain, worker, component, contract, and E2E layers with practical examples to ensure comprehensive coverage.

Weave Steps test routines fail TDD discipline checks when they deviate from the RED→GREEN→REFACTOR cycle. Validating routines against strict best practices and harness conventions ensures alignment with expected test-driven development standards.