From 35ad2f3f82fcf8db9765f73367423a95db15e8de Mon Sep 17 00:00:00 2001 From: Sallvainian Date: Wed, 25 Feb 2026 00:05:40 -0500 Subject: [PATCH] docs: align testing page workflow sequence with workflow map The "How Testing Fits into Workflows" section in testing.md described Quinn's Automate workflow as a per-story activity run before Code Review, contradicting the Workflow Map which positions it after Code Review as an epic-level activity. Updated the sequence to match the Workflow Map's authoritative ordering: per-story DS+CR, then epic-level QA, then Retrospective. Fixes #1759 Co-Authored-By: Claude Opus 4.6 --- docs/reference/testing.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/reference/testing.md b/docs/reference/testing.md index 4063ddfe1..25105ff39 100644 --- a/docs/reference/testing.md +++ b/docs/reference/testing.md @@ -95,12 +95,12 @@ TEA also supports P0-P3 risk-based prioritization and optional integrations with ## How Testing Fits into Workflows -Quinn's Automate workflow appears in Phase 4 (Implementation) of the BMad Method workflow map. A typical sequence: +Quinn's Automate workflow appears in Phase 4 (Implementation) of the BMad Method workflow map. It is designed to run **after a full epic is complete** -- once all stories have been implemented and reviewed -- to generate an end-to-end, UI-focused test suite covering the features delivered in that epic. A typical epic cycle looks like this: -1. Implement a story with the Dev workflow (`DS`) -2. Generate tests with Quinn (`QA`) or TEA's Automate workflow -3. Validate implementation with Code Review (`CR`) +1. **Per story:** Implement with the Dev workflow (`DS`), then validate with Code Review (`CR`) +2. **After the epic:** Generate end-to-end tests with Quinn (`QA`) or TEA's Automate workflow +3. **Wrap up:** Run Retrospective to capture lessons learned Quinn works directly from source code without loading planning documents (PRD, architecture). TEA workflows can integrate with upstream planning artifacts for traceability. -For more on where testing fits in the overall process, see the [Workflow Map](./workflow-map.md). +For the full Phase 4 sequence, see the [Workflow Map](./workflow-map.md).