bmm-opencode 1.5.0 → 1.6.0

package/_bmad/tea/workflows/testarch/automate/steps-c/step-03b-subprocess-e2e.md

@@ -0,0 +1,181 @@
+---
+name: 'step-03b-subprocess-e2e'
+description: 'Subprocess: Generate E2E tests only'
+subprocess: true
+outputFile: '/tmp/tea-automate-e2e-tests-{{timestamp}}.json'
+---
+
+# Subprocess 3B: Generate E2E Tests
+
+## SUBPROCESS CONTEXT
+
+This is an **isolated subprocess** running in parallel with API test generation.
+
+**What you have from parent workflow:**
+
+- Target features/user journeys identified in Step 2
+- Knowledge fragments loaded: fixture-architecture, network-first, selector-resilience
+- Config: test framework, Playwright Utils enabled/disabled
+- Coverage plan: which user journeys need E2E testing
+
+**Your task:** Generate E2E tests ONLY (not API, not fixtures, not other test types).
+
+---
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read this entire subprocess file before acting
+- ✅ Generate E2E tests ONLY
+- ✅ Output structured JSON to temp file
+- ✅ Follow knowledge fragment patterns
+- ❌ Do NOT generate API tests (that's subprocess 3A)
+- ❌ Do NOT run tests (that's step 4)
+- ❌ Do NOT generate fixtures yet (that's step 3C aggregation)
+
+---
+
+## SUBPROCESS TASK
+
+### 1. Identify User Journeys
+
+From the coverage plan (Step 2 output), identify:
+
+- Which user journeys need E2E coverage
+- Critical user paths (authentication, checkout, profile, etc.)
+- UI interactions required
+- Expected visual states
+
+### 2. Generate E2E Test Files
+
+For each user journey, create test file in `tests/e2e/[feature].spec.ts`:
+
+**Test Structure:**
+
+```typescript
+import { test, expect } from '@playwright/test';
+
+test.describe('[Feature] E2E User Journey', () => {
+  test('[P0] should complete [user journey]', async ({ page }) => {
+    // Navigate to starting point
+    await page.goto('/feature');
+
+    // Interact with UI
+    await page.getByRole('button', { name: 'Submit' }).click();
+
+    // Assert expected state
+    await expect(page.getByText('Success')).toBeVisible();
+  });
+
+  test('[P1] should handle [edge case]', async ({ page }) => {
+    // Test edge case scenario
+  });
+});
+```
+
+**Requirements:**
+
+- ✅ Follow fixture architecture patterns (from fixture-architecture fragment)
+- ✅ Use network-first patterns: intercept before navigate (from network-first fragment)
+- ✅ Use resilient selectors: getByRole, getByText, getByLabel (from selector-resilience fragment)
+- ✅ Include priority tags [P0], [P1], [P2], [P3]
+- ✅ Test complete user journeys (not isolated clicks)
+- ✅ Use proper TypeScript types
+- ✅ Deterministic waits (no hard sleeps, use expect().toBeVisible())
+
+### 3. Track Fixture Needs
+
+Identify fixtures needed for E2E tests:
+
+- Page object models (if complex)
+- Authentication fixtures (logged-in user state)
+- Network mocks/intercepts
+- Test data fixtures
+
+**Do NOT create fixtures yet** - just track what's needed for aggregation step.
+
+---
+
+## OUTPUT FORMAT
+
+Write JSON to temp file: `/tmp/tea-automate-e2e-tests-{{timestamp}}.json`
+
+```json
+{
+  "success": true,
+  "subprocess": "e2e-tests",
+  "tests": [
+    {
+      "file": "tests/e2e/authentication.spec.ts",
+      "content": "[full TypeScript test file content]",
+      "description": "E2E tests for user authentication journey",
+      "priority_coverage": {
+        "P0": 2,
+        "P1": 3,
+        "P2": 2,
+        "P3": 0
+      }
+    },
+    {
+      "file": "tests/e2e/checkout.spec.ts",
+      "content": "[full TypeScript test file content]",
+      "description": "E2E tests for checkout journey",
+      "priority_coverage": {
+        "P0": 3,
+        "P1": 2,
+        "P2": 1,
+        "P3": 0
+      }
+    }
+  ],
+  "fixture_needs": ["authenticatedUserFixture", "paymentMockFixture", "checkoutDataFixture"],
+  "knowledge_fragments_used": ["fixture-architecture", "network-first", "selector-resilience"],
+  "test_count": 15,
+  "summary": "Generated 15 E2E test cases covering 5 user journeys"
+}
+```
+
+**On Error:**
+
+```json
+{
+  "success": false,
+  "subprocess": "e2e-tests",
+  "error": "Error message describing what went wrong",
+  "partial_output": {
+    /* any tests generated before error */
+  }
+}
+```
+
+---
+
+## EXIT CONDITION
+
+Subprocess completes when:
+
+- ✅ All user journeys have E2E test files generated
+- ✅ All tests follow knowledge fragment patterns
+- ✅ JSON output written to temp file
+- ✅ Fixture needs tracked
+
+**Subprocess terminates here.** Parent workflow will read output and proceed to aggregation.
+
+---
+
+## 🚨 SUBPROCESS SUCCESS METRICS
+
+### ✅ SUCCESS:
+
+- All E2E tests generated following patterns
+- JSON output valid and complete
+- No API/component/unit tests included (out of scope)
+- Resilient selectors used (getByRole, getByText)
+- Network-first patterns applied (intercept before navigate)
+
+### ❌ FAILURE:
+
+- Generated tests other than E2E tests
+- Did not follow knowledge fragment patterns
+- Invalid or missing JSON output
+- Ran tests (not subprocess responsibility)
+- Used brittle selectors (CSS classes, XPath)

package/_bmad/tea/workflows/testarch/automate/steps-c/step-03c-aggregate.md

@@ -0,0 +1,300 @@
+---
+name: 'step-03c-aggregate'
+description: 'Aggregate subprocess outputs and complete test infrastructure'
+nextStepFile: './step-04-validate-and-summarize.md'
+---
+
+# Step 3C: Aggregate Test Generation Results
+
+## STEP GOAL
+
+Read outputs from parallel subprocesses (API + E2E test generation), aggregate results, and create supporting infrastructure (fixtures, helpers).
+
+---
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- ✅ Read subprocess outputs from temp files
+- ✅ Generate shared fixtures based on fixture needs from both subprocesses
+- ✅ Write all generated test files to disk
+- ❌ Do NOT regenerate tests (use subprocess outputs)
+- ❌ Do NOT run tests yet (that's step 4)
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Record outputs before proceeding
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, subprocess outputs from temp files
+- Focus: aggregation and fixture generation only
+- Limits: do not execute future steps
+- Dependencies: Step 3A and 3B subprocess outputs
+
+---
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Read Subprocess Outputs
+
+**Read API test subprocess output:**
+
+```javascript
+const apiTestsPath = '/tmp/tea-automate-api-tests-{{timestamp}}.json';
+const apiTestsOutput = JSON.parse(fs.readFileSync(apiTestsPath, 'utf8'));
+```
+
+**Read E2E test subprocess output:**
+
+```javascript
+const e2eTestsPath = '/tmp/tea-automate-e2e-tests-{{timestamp}}.json';
+const e2eTestsOutput = JSON.parse(fs.readFileSync(e2eTestsPath, 'utf8'));
+```
+
+**Verify both subprocesses succeeded:**
+
+- Check `apiTestsOutput.success === true`
+- Check `e2eTestsOutput.success === true`
+- If either failed, report error and stop (don't proceed)
+
+---
+
+### 2. Write All Test Files to Disk
+
+**Write API test files:**
+
+```javascript
+apiTestsOutput.tests.forEach((test) => {
+  fs.writeFileSync(test.file, test.content, 'utf8');
+  console.log(`✅ Created: ${test.file}`);
+});
+```
+
+**Write E2E test files:**
+
+```javascript
+e2eTestsOutput.tests.forEach((test) => {
+  fs.writeFileSync(test.file, test.content, 'utf8');
+  console.log(`✅ Created: ${test.file}`);
+});
+```
+
+---
+
+### 3. Aggregate Fixture Needs
+
+**Collect all fixture needs from both subprocesses:**
+
+```javascript
+const allFixtureNeeds = [...apiTestsOutput.fixture_needs, ...e2eTestsOutput.fixture_needs];
+
+// Remove duplicates
+const uniqueFixtures = [...new Set(allFixtureNeeds)];
+```
+
+**Categorize fixtures:**
+
+- **Authentication fixtures:** authToken, authenticatedUserFixture, etc.
+- **Data factories:** userDataFactory, productDataFactory, etc.
+- **Network mocks:** paymentMockFixture, apiResponseMocks, etc.
+- **Test helpers:** wait/retry/assertion helpers
+
+---
+
+### 4. Generate Fixture Infrastructure
+
+**Create or update fixture files based on needs:**
+
+**A) Authentication Fixtures** (`tests/fixtures/auth.ts`):
+
+```typescript
+import { test as base } from '@playwright/test';
+
+export const test = base.extend({
+  authenticatedUser: async ({ page }, use) => {
+    // Login logic
+    await page.goto('/login');
+    await page.fill('[name="email"]', 'test@example.com');
+    await page.fill('[name="password"]', 'password');
+    await page.click('button[type="submit"]');
+    await page.waitForURL('/dashboard');
+
+    await use(page);
+  },
+
+  authToken: async ({ request }, use) => {
+    // Get auth token for API tests
+    const response = await request.post('/api/auth/login', {
+      data: { email: 'test@example.com', password: 'password' },
+    });
+    const { token } = await response.json();
+
+    await use(token);
+  },
+});
+```
+
+**B) Data Factories** (`tests/fixtures/data-factories.ts`):
+
+```typescript
+import { faker } from '@faker-js/faker';
+
+export const createUserData = (overrides = {}) => ({
+  name: faker.person.fullName(),
+  email: faker.internet.email(),
+  ...overrides,
+});
+
+export const createProductData = (overrides = {}) => ({
+  name: faker.commerce.productName(),
+  price: faker.number.int({ min: 10, max: 1000 }),
+  ...overrides,
+});
+```
+
+**C) Network Mocks** (`tests/fixtures/network-mocks.ts`):
+
+```typescript
+import { Page } from '@playwright/test';
+
+export const mockPaymentSuccess = async (page: Page) => {
+  await page.route('/api/payment/**', (route) => {
+    route.fulfill({
+      status: 200,
+      body: JSON.stringify({ success: true, transactionId: '12345' }),
+    });
+  });
+};
+```
+
+**D) Helper Utilities** (`tests/fixtures/helpers.ts`):
+
+```typescript
+import { expect, Page } from '@playwright/test';
+
+export const waitForApiResponse = async (page: Page, urlPattern: string) => {
+  return page.waitForResponse((response) => response.url().includes(urlPattern) && response.ok());
+};
+```
+
+---
+
+### 5. Calculate Summary Statistics
+
+**Aggregate test counts:**
+
+```javascript
+const summary = {
+  total_tests: apiTestsOutput.test_count + e2eTestsOutput.test_count,
+  api_tests: apiTestsOutput.test_count,
+  e2e_tests: e2eTestsOutput.test_count,
+  fixtures_created: uniqueFixtures.length,
+  api_test_files: apiTestsOutput.tests.length,
+  e2e_test_files: e2eTestsOutput.tests.length,
+  priority_coverage: {
+    P0: /* sum P0 tests from both */,
+    P1: /* sum P1 tests from both */,
+    P2: /* sum P2 tests from both */,
+    P3: /* sum P3 tests from both */
+  },
+  knowledge_fragments_used: [
+    ...apiTestsOutput.knowledge_fragments_used,
+    ...e2eTestsOutput.knowledge_fragments_used
+  ],
+  subprocess_execution: 'PARALLEL (API + E2E)',
+  performance_gain: '~50% faster than sequential'
+};
+```
+
+**Store summary for Step 4:**
+Save summary to temp file for validation step:
+
+```javascript
+fs.writeFileSync('/tmp/tea-automate-summary-{{timestamp}}.json', JSON.stringify(summary, null, 2), 'utf8');
+```
+
+---
+
+### 6. Optional Cleanup
+
+**Clean up subprocess temp files** (optional - can keep for debugging):
+
+```javascript
+fs.unlinkSync(apiTestsPath);
+fs.unlinkSync(e2eTestsPath);
+console.log('✅ Subprocess temp files cleaned up');
+```
+
+---
+
+## OUTPUT SUMMARY
+
+Display to user:
+
+```
+✅ Test Generation Complete (Parallel Execution)
+
+📊 Summary:
+- Total Tests: {total_tests}
+  - API Tests: {api_tests} ({api_test_files} files)
+  - E2E Tests: {e2e_tests} ({e2e_test_files} files)
+- Fixtures Created: {fixtures_created}
+- Priority Coverage:
+  - P0 (Critical): {P0} tests
+  - P1 (High): {P1} tests
+  - P2 (Medium): {P2} tests
+  - P3 (Low): {P3} tests
+
+🚀 Performance: Parallel execution ~50% faster than sequential
+
+📂 Generated Files:
+- tests/api/[feature].spec.ts
+- tests/e2e/[feature].spec.ts
+- tests/fixtures/auth.ts
+- tests/fixtures/data-factories.ts
+- tests/fixtures/network-mocks.ts
+- tests/fixtures/helpers.ts
+
+✅ Ready for validation (Step 4)
+```
+
+---
+
+## EXIT CONDITION
+
+Proceed to Step 4 when:
+
+- ✅ All test files written to disk (API + E2E)
+- ✅ All fixtures and helpers created
+- ✅ Summary statistics calculated and saved
+- ✅ Output displayed to user
+
+Load next step: `{nextStepFile}`
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Both subprocesses succeeded
+- All test files written to disk
+- Fixtures generated based on subprocess needs
+- Summary complete and accurate
+
+### ❌ SYSTEM FAILURE:
+
+- One or both subprocesses failed
+- Test files not written to disk
+- Fixtures missing or incomplete
+- Summary missing or inaccurate
+
+**Master Rule:** Do NOT proceed to Step 4 if aggregation incomplete.

package/_bmad/tea/workflows/testarch/automate/steps-c/step-04-validate-and-summarize.md

@@ -0,0 +1,69 @@
+---
+name: 'step-04-validate-and-summarize'
+description: 'Validate outputs and produce automation summary'
+outputFile: '{output_folder}/automation-summary.md'
+---
+
+# Step 4: Validate & Summarize
+
+## STEP GOAL
+
+Validate generated outputs and produce a concise automation summary.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- ✅ Validate against the checklist before completion
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Record outputs before proceeding
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, loaded artifacts, and knowledge fragments
+- Focus: this step's goal only
+- Limits: do not execute future steps
+- Dependencies: prior steps' outputs (if any)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+## 1. Validate
+
+Use `checklist.md` to validate:
+
+- Framework readiness
+- Coverage mapping
+- Test quality and structure
+- Fixtures, factories, helpers
+
+Fix gaps before proceeding.
+
+---
+
+## 2. Summary Output
+
+Write `{outputFile}` including:
+
+- Coverage plan by test level and priority
+- Files created/updated
+- Key assumptions and risks
+- Next recommended workflow (e.g., `test-review` or `trace`)
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Step completed in full with required outputs
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped sequence steps or missing outputs
+  **Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/tea/workflows/testarch/automate/steps-e/step-01-assess.md

@@ -0,0 +1,65 @@
+---
+name: 'step-01-assess'
+description: 'Load an existing output for editing'
+nextStepFile: './step-02-apply-edit.md'
+---
+
+# Step 1: Assess Edit Target
+
+## STEP GOAL:
+
+Identify which output should be edited and load it.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Master Test Architect
+
+### Step-Specific Rules:
+
+- 🎯 Ask the user which output file to edit
+- 🚫 Do not edit until target is confirmed
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+
+## CONTEXT BOUNDARIES:
+
+- Available context: existing outputs
+- Focus: select edit target
+- Limits: no edits yet
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Identify Target
+
+Ask the user to provide the output file path or select from known outputs.
+
+### 2. Load Target
+
+Read the provided output file in full.
+
+### 3. Confirm
+
+Confirm the target and proceed to edit.
+
+Load next step: `{nextStepFile}`
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Target identified and loaded
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding without a confirmed target

package/_bmad/tea/workflows/testarch/automate/steps-e/step-02-apply-edit.md

@@ -0,0 +1,60 @@
+---
+name: 'step-02-apply-edit'
+description: 'Apply edits to the selected output'
+---
+
+# Step 2: Apply Edits
+
+## STEP GOAL:
+
+Apply the requested edits to the selected output and confirm changes.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Master Test Architect
+
+### Step-Specific Rules:
+
+- 🎯 Only apply edits explicitly requested by the user
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+
+## CONTEXT BOUNDARIES:
+
+- Available context: selected output and user changes
+- Focus: apply edits only
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly.
+
+### 1. Confirm Requested Changes
+
+Restate what will be changed and confirm.
+
+### 2. Apply Changes
+
+Update the output file accordingly.
+
+### 3. Report
+
+Summarize the edits applied.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Changes applied and confirmed
+
+### ❌ SYSTEM FAILURE:
+
+- Unconfirmed edits or missing update