---
title: TEA Test Design -> BMAD Handoff Document
version: "1.0"
workflowType: testarch-test-design-handoff
inputDocuments:
  - D:\Development\Tracking_Kits\_bmad-output\test-artifacts\test-design-architecture.md
  - D:\Development\Tracking_Kits\_bmad-output\test-artifacts\test-design-qa.md
sourceWorkflow: testarch-test-design
generatedBy: TEA Master Test Architect
generatedAt: "2026-03-17T00:00:00"
projectName: workspace
---

# TEA -> BMAD Integration Handoff

## Purpose

This document bridges the purple-envelope regression test design with future BMAD epic/story work so the current behavior contract is preserved during implementation.

## TEA Artifacts Inventory

| Artifact | Path | BMAD Integration Point |
| --- | --- | --- |
| Test Design Architecture | `D:\Development\Tracking_Kits\_bmad-output\test-artifacts\test-design-architecture.md` | Architectural blockers, risk mitigation, testability requirements |
| Test Design QA | `D:\Development\Tracking_Kits\_bmad-output\test-artifacts\test-design-qa.md` | Story acceptance criteria and regression scenario coverage |
| Risk Assessment | embedded in both docs | Epic quality gates and story priority |

## Epic-Level Integration Guidance

### Risk References

- **R-001 / R-002** must be treated as epic-level quality blockers because ordering or aggregation defects change operator-facing output.
- **R-006** must be scheduled as enabling work before expecting reliable automated regression coverage.

### Quality Gates

- No story touching the purple-envelope edit page is complete until mixed-format precinct ordering is proven against seeded data.
- No story touching the report query/view is complete until ballot low/high aggregation is verified.
- Print-affecting changes require a manual Windows/IIS print smoke before release.

## Story-Level Integration Guidance

### P0/P1 Test Scenarios -> Story Acceptance Criteria

- The purple-envelope report renders jurisdiction, JCode, and election date exactly as currently approved.
- Precincts sort in the frozen ascending order for zero-padded, numeric, and alpha-suffixed values.
- Each precinct shows the correct low/high ballot number range.
- Kit-wide and precinct-specific color updates still work on the same screen.
- Empty precinct datasets show the current no-data row without error.

### Data-TestId Requirements

- Not applicable for Classic ASP in the current implementation.
- Prefer stable HTML markers, predictable headings, and table structure for server-render assertions.

## Risk-to-Story Mapping

| Risk ID | Category | P×I | Recommended Story/Epic | Test Level |
| --- | --- | --- | --- | --- |
| R-001 | DATA | 2x3 | Purple-envelope report ordering contract | Integration |
| R-002 | DATA | 2x3 | Purple-envelope ballot aggregation contract | Integration |
| R-003 | BUS | 2x2 | Election date render/fallback behavior | Integration |
| R-004 | OPS | 2x2 | Print-only report markup and manual print smoke | Integration + Manual |
| R-005 | BUS | 2x2 | Preserve color-assignment workflows on same screen | Integration |
| R-006 | TECH | 3x2 | Disposable MDB/reset harness for regression suite | Enabler |
| R-007 | BUS | 2x2 | Empty-state render contract | Integration |

## Recommended BMAD -> TEA Workflow Sequence

1. TEA Test Design (`TD`) -> complete
2. BMAD Create Epics & Stories -> include regression-preservation stories and test-harness enabler work
3. TEA ATDD (`AT`) -> generate failing checks for P0 report-ordering and aggregation scenarios
4. BMAD Implementation -> add fixtures/tests/harness work
5. TEA Automate (`TA`) -> expand the suite beyond the initial P0/P1 checks
6. TEA Trace (`TR`) -> verify risk coverage completeness

## Phase Transition Quality Gates

| From Phase | To Phase | Gate Criteria |
| --- | --- | --- |
| Test Design | Epic/Story Creation | R-001, R-002, and R-006 mitigation work represented in planning |
| Epic/Story Creation | ATDD | P0 scenarios for ordering and aggregation translated into executable checks |
| ATDD | Implementation | Seed fixtures and disposable DB approach agreed |
| Implementation | Test Automation | Automated P0 checks passing |
| Test Automation | Release | Manual print smoke complete for print-affecting changes |
