@cregis-dev/cckit 0.4.1 → 0.5.0

package/templates/bmad/tea/workflows/testarch/teach-me-testing/steps-c/step-04-session-05.md

@@ -1,234 +0,0 @@
----
-name: 'step-04-session-05'
-description: 'Session 5: ATDD & Automate - TDD red-green approach, generate tests (60 min)'
-
-progressFile: '{test_artifacts}/teaching-progress/{user_name}-tea-progress.yaml'
-sessionNotesTemplate: '../templates/session-notes-template.md'
-sessionNotesFile: '{test_artifacts}/tea-academy/{user_name}/session-05-notes.md'
-nextStepFile: './step-03-session-menu.md'
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 4: Session 5 - ATDD & Automate
-
-## STEP GOAL:
-
-To teach ATDD (red-green TDD) and Automate workflows for test generation in a 60-minute session.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read complete step file before action
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In {communication_language}
-
-### Role Reinforcement:
-
-- ✅ Master Test Architect and Teaching Guide
-- ✅ Collaborative learning
-
-### Step-Specific Rules:
-
-- 🎯 Focus on Session 5 (ATDD & Automate)
-- 💬 Teach TDD approach
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load docs just-in-time
-- 💾 Generate notes
-- 📖 Update progress
-- ⏭️ Return to hub
-
-## MANDATORY SEQUENCE
-
-### 1. Welcome
-
-"🧪 **Session 5: ATDD & Automate** (60 minutes)
-
-**Objective:** Generate tests with TDD red-green approach
-
-**What you'll learn:**
-
-- ATDD workflow (failing tests first)
-- Automate workflow (expand coverage)
-- Component TDD
-- API testing patterns
-
-Let's generate some tests!"
-
-### 2. Update Progress (Started)
-
-Load {progressFile} and update session-05-atdd-automate:
-
-- Set `status: 'in-progress'`
-- Set `started_date: {current_date}` if not already set
-
-Save the updated progress file.
-
-### 3. Teaching: ATDD Workflow
-
-"### 🔴 ATDD: Acceptance-Driven Test Development
-
-**TDD Red Phase:** Write failing tests FIRST
-
-**ATDD Workflow:**
-
-1. **Preflight:** Check prerequisites
-2. **Test Strategy:** Define what to test
-3. **Generate FAILING Tests:** Red phase (tests fail because code doesn't exist yet)
-4. **Implement Code:** Green phase (make tests pass)
-
-**Why Failing Tests First:**
-
-- Validates tests actually test something
-- Prevents false positives
-- Drives implementation (tests define behavior)
-
-{Role-adapted example}
-
-**Documentation:** <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/how-to/workflows/run-atdd/>"
-
-### 4. Teaching: Automate Workflow
-
-"### 🤖 Automate: Expand Test Coverage
-
-**Purpose:** Generate tests for existing features
-
-**Automate Workflow:**
-
-1. **Identify Targets:** What needs testing
-2. **Generate Tests:** API and/or E2E tests
-3. **Review & Run:** Tests should pass (code already exists)
-
-**Difference from ATDD:**
-
-- ATDD: Tests first, then code (red → green)
-- Automate: Code first, then tests (coverage expansion)
-
-{Role-adapted example}
-
-**Documentation:** <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/how-to/workflows/run-automate/>"
-
-### 5. Teaching: Component TDD
-
-"### 🔄 Component TDD Red-Green Loop
-
-**Pattern:**
-
-1. **Red:** Write failing test
-2. **Green:** Minimal code to pass
-3. **Refactor:** Improve code, tests stay green
-4. **Repeat:** Next requirement
-
-**Example:**
-
-```typescript
-// RED: Test fails (function doesn't exist)
-test('calculates total price', () => {
-  expect(calculateTotal([10, 20])).toBe(30);
-});
-
-// GREEN: Minimal implementation
-function calculateTotal(prices) {
-  return prices.reduce((a, b) => a + b, 0);
-}
-
-// REFACTOR: Add validation, tests still green
-```
-
-{Role-adapted example}
-
-**Knowledge Fragment:** component-tdd.md"
-
-### 6. Teaching: API Testing Patterns
-
-"### 🌐 API Testing Patterns
-
-**Pure API Testing (no browser):**
-
-- Fast execution
-- Test business logic
-- Validate responses
-- Schema validation
-
-**Pattern:**
-
-```typescript
-test('GET /users returns user list', async ({ request }) => {
-  const response = await request.get('/api/users');
-  expect(response.ok()).toBeTruthy();
-  const users = await response.json();
-  expect(users).toHaveLength(10);
-});
-```
-
-{Role-adapted example}
-
-**Knowledge Fragment:** api-testing-patterns.md, api-request.md"
-
-### 7. Quiz (3 questions)
-
-**Q1:** "What is the 'red' phase in TDD?
-A) Tests fail (code doesn't exist yet)
-B) Tests pass
-C) Code is refactored
-D) Tests are deleted"
-
-Correct: A
-
-**Q2:** "What's the difference between ATDD and Automate workflows?
-A) ATDD generates E2E, Automate generates API tests
-B) ATDD writes tests first (red phase), Automate tests existing code
-C) ATDD is faster than Automate
-D) They're the same workflow"
-
-Correct: B
-
-**Q3:** "Why use pure API tests without a browser?
-A) They look prettier
-B) They're easier to debug
-C) They're faster and test business logic directly
-D) They're required by TEA"
-
-Correct: C
-
-Calculate score, handle <70% retry.
-
-### 8. Generate Session Notes
-
-Create {sessionNotesFile} with Session 5 content:
-
-- ATDD workflow (red-green TDD)
-- Automate workflow (coverage expansion)
-- Component TDD
-- API testing patterns
-- Docs: ATDD, Automate
-- Fragments: component-tdd.md, api-testing-patterns.md, api-request.md
-- Quiz results
-
-### 9. Update Progress (Completed)
-
-Update session-05-atdd-automate: completed, score, notes.
-Increment sessions_completed, update percentage.
-Append 'step-04-session-05' to stepsCompleted.
-Set next_recommended: 'session-06-quality-trace'.
-
-### 10. Complete Message
-
-"🎉 **Session 5 Complete!** Score: {score}/100
-You can now generate tests with ATDD and Automate!
-Progress: {completion_percentage}%"
-
-### 11. Menu
-
-[A] Advanced Elicitation [P] Party Mode [C] Continue to Session Menu
-
-Return to {nextStepFile}.
-
----
-
-## 🚨 SUCCESS METRICS
-
-✅ ATDD and Automate taught, TDD explained, quiz passed, notes generated, progress updated, returned to hub.

package/templates/bmad/tea/workflows/testarch/teach-me-testing/steps-c/step-04-session-06.md

@@ -1,209 +0,0 @@
----
-name: 'step-04-session-06'
-description: 'Session 6: Quality & Trace - Test review, traceability, quality metrics (45 min)'
-
-progressFile: '{test_artifacts}/teaching-progress/{user_name}-tea-progress.yaml'
-sessionNotesTemplate: '../templates/session-notes-template.md'
-sessionNotesFile: '{test_artifacts}/tea-academy/{user_name}/session-06-notes.md'
-nextStepFile: './step-03-session-menu.md'
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 4: Session 6 - Quality & Trace
-
-## STEP GOAL:
-
-To teach test quality auditing and requirements traceability using Test Review and Trace workflows in a 45-minute session.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate _unsolicited_ content without user input (session flow content is allowed once session begins)
-- 📖 CRITICAL: Read complete step file before action
-- ✅ SPEAK OUTPUT In {communication_language}
-
-### Role Reinforcement:
-
-- ✅ Master Test Architect and Teaching Guide
-- ✅ Collaborative learning
-
-### Step-Specific Rules:
-
-- 🎯 Focus on Session 6 (Quality & Trace)
-- 💬 Teach quality metrics
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load docs just-in-time
-- 💾 Generate notes
-- 📖 Update progress
-- ⏭️ Return to hub
-
-## MANDATORY SEQUENCE
-
-### 1. Welcome
-
-"🧪 **Session 6: Quality & Trace** (45 minutes)
-
-**Objective:** Audit quality and ensure traceability
-
-**What you'll learn:**
-
-- Test Review workflow (quality scoring)
-- 5 dimensions of test quality
-- Trace workflow (requirements traceability)
-- Release gate decisions
-
-Let's ensure quality!"
-
-### 2. Update Progress (Started)
-
-Set session-06-quality-trace `status: 'in-progress'`.
-
-### 3. Teaching: Test Review Workflow
-
-"### 🔍 Test Review Workflow
-
-**Purpose:** Audit test quality with 0-100 scoring
-
-**5 Dimensions of Quality:**
-
-**1. Determinism (0-100)**
-
-- Tests pass/fail consistently
-- No flakiness, no randomness
-- Proper async handling
-
-**2. Isolation (0-100)**
-
-- Tests run independently
-- No shared state
-- Parallelizable
-
-**3. Assertions (0-100)**
-
-- Correct checks for expected behavior
-- Meaningful assertions (not just presence)
-- Fails for the right reasons
-
-**4. Structure (0-100)**
-
-- Readable test code
-- Clear organization and naming
-- Minimal duplication
-
-**5. Performance (0-100)**
-
-- Test execution speed
-- Resource usage
-- Parallel efficiency
-
-**Overall Score = Average of 5 dimensions**
-
-{Role-adapted example}
-
-**Documentation:** <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/how-to/workflows/run-test-review/>"
-
-### 4. Teaching: Trace Workflow
-
-"### 🔗 Trace Workflow: Requirements Traceability
-
-**Purpose:** Map tests to requirements, make release gate decision
-
-**Trace Workflow:**
-
-1. **Load Context:** Understand acceptance criteria
-2. **Discover Tests:** Find all test files
-3. **Map Criteria:** Link tests to requirements
-4. **Analyze Gaps:** What's not tested?
-5. **Gate Decision:** GREEN (ship) or RED (block)
-
-**Release Gate Logic:**
-
-- **GREEN:** All P0/P1 criteria have tests, gaps are P2/P3
-- **YELLOW:** Some P1 gaps, assess risk
-- **RED:** P0 gaps exist, DO NOT SHIP
-
-{Role-adapted example}
-
-**Documentation:** <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/how-to/workflows/run-trace/>"
-
-### 5. Teaching: Quality Metrics
-
-"### 📊 Quality Metrics That Matter
-
-**Track:**
-
-- **P0/P1 Coverage %** (not total line coverage)
-- **Flakiness Rate** (flaky tests / total tests)
-- **Test Execution Time** (feedback loop speed)
-- **Determinism Score** (from Test Review)
-
-**Don't Track (Vanity Metrics):**
-
-- Total line coverage % (tells you nothing about risk)
-- Number of tests (quantity ≠ quality)
-- Test file count (irrelevant)
-
-{Role-adapted example}
-
-**Goal:** High P0/P1 coverage, zero flakiness, fast execution."
-
-### 6. Quiz (3 questions)
-
-**Q1:** "What are the 5 dimensions in Test Review workflow?
-A) Speed, cost, coverage, bugs, time
-B) Determinism, Isolation, Assertions, Structure, Performance
-C) Unit, integration, E2E, manual, exploratory
-D) P0, P1, P2, P3, P4"
-
-Correct: B
-
-**Q2:** "When should the Trace workflow gate decision be RED (block release)?
-A) Any test failures exist
-B) P0 gaps exist (critical requirements not tested)
-C) Code coverage is below 80%
-D) Tests are slow"
-
-Correct: B
-
-**Q3:** "Which metric matters most for quality?
-A) Total line coverage %
-B) Number of tests written
-C) P0/P1 coverage %
-D) Test file count"
-
-Correct: C
-
-Calculate score, handle <70% retry.
-
-### 7. Generate Session Notes
-
-Create {sessionNotesFile} with Session 6 content, Test Review + Trace workflows, quality metrics.
-
-### 8. Update Progress (Completed)
-
-Update session-06-quality-trace: completed, score, notes.
-Increment sessions_completed, update percentage.
-Append 'step-04-session-06' to stepsCompleted.
-Set next_recommended: 'session-07-advanced'.
-
-### 9. Complete Message
-
-"🎉 **Session 6 Complete!** Score: {score}/100
-You can now audit quality and ensure traceability!
-Progress: {completion_percentage}%"
-
-### 10. Menu
-
-[A] Advanced Elicitation [P] Party Mode [C] Continue to Session Menu
-
-Return to {nextStepFile}.
-
----
-
-## 🚨 SUCCESS METRICS
-
-✅ Test Review and Trace taught, quality dimensions explained, quiz passed, notes generated, returned to hub.

package/templates/bmad/tea/workflows/testarch/teach-me-testing/steps-c/step-04-session-07.md

@@ -1,212 +0,0 @@
----
-name: 'step-04-session-07'
-description: 'Session 7: Advanced Patterns - Menu-driven knowledge fragment exploration (ongoing)'
-
-progressFile: '{test_artifacts}/teaching-progress/{user_name}-tea-progress.yaml'
-sessionNotesTemplate: '../templates/session-notes-template.md'
-sessionNotesFile: '{test_artifacts}/tea-academy/{user_name}/session-07-notes.md'
-nextStepFile: './step-03-session-menu.md'
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 4: Session 7 - Advanced Patterns
-
-## STEP GOAL:
-
-To provide menu-driven exploration of 35 TEA knowledge fragments organized by category, allowing deep-dive into specific advanced topics on-demand.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read complete step file before action
-- ✅ SPEAK OUTPUT In {communication_language}
-
-### Role Reinforcement:
-
-- ✅ Master Test Architect and Teaching Guide
-- ✅ Collaborative exploration
-
-### Step-Specific Rules:
-
-- 🎯 Focus on Session 7 (Advanced Patterns exploration)
-- 💬 Menu-driven, user chooses topics
-- 📚 This session is ONGOING - users can explore multiple fragments
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Display fragment categories
-- 💾 Generate notes after exploration
-- 📖 Update progress when user exits
-- ⏭️ Return to hub when done
-
-## MANDATORY SEQUENCE
-
-### 1. Welcome
-
-"🧪 **Session 7: Advanced Patterns** (Ongoing Exploration)
-
-**Objective:** Deep-dive into 34 TEA knowledge fragments
-
-**This session is different:**
-
-- Menu-driven exploration (you choose topics)
-- Explore as many fragments as you want
-- Can revisit this session anytime
-- No quiz - this is reference learning
-
-**35 Knowledge Fragments organized by category:**
-
-Let's explore!"
-
-### 2. Update Progress (Started)
-
-Set session-07-advanced `status: 'in-progress'` (only first time).
-
-### 3. Display Knowledge Fragment Categories
-
-"### 📚 Knowledge Fragment Categories
-
-**1. Testing Patterns (9 fragments)**
-
-- fixture-architecture.md - Composable fixture patterns
-- fixtures-composition.md - mergeTests composition patterns
-- network-first.md - Network interception safeguards
-- data-factories.md - Data seeding & setup
-- component-tdd.md - TDD red-green loop
-- api-testing-patterns.md - Pure API testing
-- test-healing-patterns.md - Auto-fix common failures
-- selector-resilience.md - Robust selectors
-- timing-debugging.md - Race condition fixes
-
-**2. Playwright Utils (11 fragments)**
-
-- overview.md - Playwright Utils overview
-- api-request.md - Typed HTTP client
-- network-recorder.md - HAR record/playback
-- intercept-network-call.md - Network spy/stub
-- recurse.md - Async polling
-- log.md - Report logging
-- file-utils.md - CSV/XLSX/PDF validation
-- burn-in.md - Smart test selection
-- network-error-monitor.md - HTTP error detection
-- contract-testing.md - Pact integration
-- visual-debugging.md - Trace viewer workflows
-
-**3. Configuration & Governance (6 fragments)**
-
-- playwright-config.md - Environment & timeout guardrails
-- ci-burn-in.md - CI orchestration
-- selective-testing.md - Tag/grep filters
-- feature-flags.md - Governance & cleanup
-- risk-governance.md - Scoring matrix & gates
-- adr-quality-readiness-checklist.md - Quality readiness checklist
-
-**4. Quality Frameworks (5 fragments)**
-
-- test-quality.md - DoD execution limits
-- test-levels-framework.md - Unit/Integration/E2E
-- test-priorities-matrix.md - P0-P3 coverage targets
-- probability-impact.md - Probability × impact scoring
-- nfr-criteria.md - NFR assessment definitions
-
-**5. Authentication & Security (3 fragments)**
-
-- email-auth.md - Magic link extraction
-- auth-session.md - Token persistence
-- error-handling.md - Exception handling
-
-**GitHub Repository:** <https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/testarch/knowledge>
-
-**Select a category (1-5) or specific fragment to explore, or [X] to finish:**"
-
-### 4. Fragment Exploration Loop
-
-**Wait for user selection.**
-
-**Handle selection:**
-
-- **IF 1-5 (category):** Display all fragments in that category with descriptions, ask which fragment to explore
-- **IF specific fragment name:** Load and present that fragment's content
-- **IF X:** Proceed to step 5 (complete session)
-- **IF Any other:** Help user, redisplay categories
-
-**For each fragment explored:**
-
-1. Present the fragment's key concepts
-2. Provide role-adapted examples
-3. Link to GitHub source
-4. Ask: "Explore another fragment? [Y/N/X to finish]"
-5. If Y: Redisplay categories
-6. If N or X: Proceed to completion
-
-**Track fragments explored** (for session notes).
-
-### 5. Session Summary
-
-After user selects X (finish exploration):
-
-"### 🎯 Session 7 Summary
-
-**Fragments Explored:** {count}
-
-{List each fragment explored}
-
-**Key Takeaways:**
-{Summarize insights from explored fragments}
-
-**Remember:** You can return to Session 7 anytime to explore more fragments!
-
-**GitHub Knowledge Base:** <https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/testarch/knowledge>"
-
-### 6. Generate Session Notes
-
-Create {sessionNotesFile} with:
-
-- Session 7 content
-- List of fragments explored
-- Key insights from each
-- GitHub links
-- No quiz (exploratory session)
-- Score: 100 (completion based, not quiz based)
-
-### 7. Update Progress (Completed)
-
-Update session-07-advanced: completed, score: 100, notes.
-Increment sessions_completed, update percentage.
-Append 'step-04-session-07' to stepsCompleted.
-
-**Check completion:**
-
-- If sessions_completed == 7: Set next_recommended: 'completion'
-- Otherwise: Recommend next incomplete session
-
-### 8. Complete Message
-
-"🎉 **Session 7 Complete!**
-
-**Fragments Explored:** {count}
-
-{If sessions_completed == 7:}
-🏆 **Congratulations!** You've completed ALL 7 sessions!
-Your completion certificate will be generated when you return to the menu.
-
-{Otherwise:}
-**Progress:** {completion_percentage}% complete ({sessions_completed} of 7 sessions)
-You can return to Session 7 anytime to explore more fragments!"
-
-### 9. Menu
-
-[A] Advanced Elicitation [P] Party Mode [C] Continue to Session Menu
-
-Return to {nextStepFile}.
-
----
-
-## 🚨 SUCCESS METRICS
-
-✅ Fragment categories displayed, user explored chosen fragments, notes generated with exploration summary, progress updated, returned to hub.
-
-**Master Rule:** This session is exploratory and repeatable. User drives exploration, workflow facilitates.