bmad-studio 0.1.0

package/_bmad/tea/workflows/testarch/bmad-teach-me-testing/checklist.md

@@ -0,0 +1,197 @@
+# Teach Me Testing - Quality Checklist
+
+## Workflow Quality Standards
+
+Use this checklist to validate the teaching workflow meets quality standards.
+
+---
+
+## Foundation Quality
+
+- [ ] **workflow.md** exists with proper frontmatter
+- [ ] Tri-modal routing logic present (Create/Edit/Validate)
+- [ ] Configuration loading references correct module (TEA)
+- [ ] First step path correct (`./steps-c/step-01-init.md`)
+- [ ] Folder structure complete (steps-c/, steps-e/, steps-v/, data/, templates/)
+
+---
+
+## Template Quality
+
+- [ ] **progress-template.yaml** has complete schema
+- [ ] All 7 sessions defined with proper structure
+- [ ] Session status tracking fields present (not-started/in-progress/completed)
+- [ ] stepsCompleted array for continuation tracking
+- [ ] **session-notes-template.md** has all required sections
+- [ ] **certificate-template.md** includes all 7 sessions
+
+---
+
+## Step File Quality (CREATE mode)
+
+### Initialization Steps
+
+- [ ] **step-01-init.md** checks for existing progress file
+- [ ] Continuation detection logic works correctly
+- [ ] **step-01b-continue.md** loads progress and routes to session menu
+- [ ] Progress dashboard displays completion status
+
+### Assessment Step
+
+- [ ] **step-02-assess.md** gathers role, experience, goals
+- [ ] Validation for role (QA/Dev/Lead/VP)
+- [ ] Validation for experience (beginner/intermediate/experienced)
+- [ ] Assessment data written to progress file
+
+### Session Menu Hub
+
+- [ ] **step-03-session-menu.md** displays all 7 sessions
+- [ ] Completion indicators shown (✓ completed, 🔄 in-progress, ⬜ not-started)
+- [ ] Branching logic routes to selected session (1-7)
+- [ ] Exit logic (X) routes to completion if all done, otherwise saves and exits
+
+### Session Steps (1-7)
+
+- [ ] Each session loads relevant TEA docs just-in-time
+- [ ] Teaching content presented (mostly autonomous)
+- [ ] Quiz validation with ≥70% threshold
+- [ ] Session notes artifact generated
+- [ ] Progress file updated (status, score, artifact path)
+- [ ] Returns to session menu hub after completion
+
+### Completion Step
+
+- [ ] **step-05-completion.md** verifies all 7 sessions complete
+- [ ] Certificate generated with accurate data
+- [ ] Final progress file update (certificate_generated: true)
+- [ ] Congratulations message shown
+
+---
+
+## Data File Quality
+
+- [ ] **curriculum.yaml** defines all 7 sessions
+- [ ] **role-paths.yaml** maps role customizations
+- [ ] **session-content-map.yaml** references TEA docs/fragments/URLs correctly
+- [ ] **quiz-questions.yaml** has questions for all sessions
+- [ ] **tea-resources-index.yaml** has complete documentation index
+
+---
+
+## Content Quality
+
+### TEA Documentation Integration
+
+- [ ] Local file paths correct (`/docs/*.md`, `/src/testarch/knowledge/*.md`)
+- [ ] Online URLs correct (<https://bmad-code-org.github.io/...>)
+- [ ] GitHub fragment links correct
+- [ ] Triple reference system (local + online + GitHub) implemented
+
+### Role-Based Content
+
+- [ ] QA examples present (practical testing focus)
+- [ ] Dev examples present (integration/TDD focus)
+- [ ] Lead examples present (architecture/patterns focus)
+- [ ] VP examples present (strategy/metrics focus)
+
+### Quiz Quality
+
+- [ ] Questions test understanding, not memorization
+- [ ] 3-5 questions per session
+- [ ] Mix of difficulty levels
+- [ ] Clear correct answers with explanations
+
+---
+
+## Error Handling
+
+- [ ] Corrupted progress file detection
+- [ ] Backup and recovery options
+- [ ] Missing TEA docs fallback (Web-Browsing)
+- [ ] Quiz failure recovery (review or continue)
+- [ ] Session interruption handling (auto-save)
+
+---
+
+## User Experience
+
+- [ ] Clear navigation instructions
+- [ ] Progress visibility (completion percentage, next recommended)
+- [ ] Auto-save after each session
+- [ ] Resume capability works seamlessly
+- [ ] Exit options clear at all decision points
+
+---
+
+## State Management
+
+- [ ] stepsCompleted array updated correctly
+- [ ] Session tracking accurate (status, dates, scores)
+- [ ] Completion percentage calculated correctly
+- [ ] Next recommended session logic works
+- [ ] lastStep and lastContinued timestamps updated
+
+---
+
+## Validation Mode
+
+- [ ] **step-v-01-validate.md** checks all quality standards
+- [ ] Generates validation report
+- [ ] Identifies issues clearly
+- [ ] Provides remediation suggestions
+
+---
+
+## Edit Mode
+
+- [ ] **step-e-01-assess-workflow.md** identifies what to edit
+- [ ] **step-e-02-apply-edits.md** applies modifications safely
+- [ ] Preserves workflow integrity during edits
+
+---
+
+## Documentation
+
+- [ ] **instructions.md** clear and complete
+- [ ] **checklist.md** (this file) comprehensive
+- [ ] README (if present) accurate
+- [ ] Inline comments in complex logic
+
+---
+
+## Performance
+
+- [ ] Just-in-time loading (not loading all docs upfront)
+- [ ] Session steps complete in reasonable time (<5 min)
+- [ ] Quiz validation fast (<1 min)
+- [ ] Progress file writes efficient
+
+---
+
+## Security
+
+- [ ] No hardcoded credentials
+- [ ] File paths use variables
+- [ ] Progress files private to user
+- [ ] No sensitive data in session notes
+
+---
+
+## Completion Criteria
+
+✅ **Workflow is ready for deployment when:**
+
+- All checkboxes above are checked
+- All step files exist and follow standards
+- All templates present and correct
+- Data files complete and accurate
+- Error handling robust
+- User experience smooth
+- Documentation complete
+
+---
+
+**Validation Date:** **\*\***\_\_\_**\*\***
+**Validated By:** **\*\***\_\_\_**\*\***
+**Issues Found:** **\*\***\_\_\_**\*\***
+**Status:** ⬜ Ready for Production | ⬜ Needs Revisions

package/_bmad/tea/workflows/testarch/bmad-teach-me-testing/data/curriculum.yaml

@@ -0,0 +1,129 @@
+# TEA Academy Curriculum Structure
+# Defines the 7-session learning path with objectives and content mappings
+
+sessions:
+  - id: session-01-quickstart
+    name: "Quick Start"
+    duration: "30 min"
+    difficulty: beginner
+    objective: "Get immediate value by seeing TEA in action"
+    description: "TEA Lite intro, run automate workflow, understand engagement models"
+    recommended_for:
+      - beginner
+      - intermediate
+      - experienced
+    prerequisites: []
+
+  - id: session-02-concepts
+    name: "Core Concepts"
+    duration: "45 min"
+    difficulty: beginner
+    objective: "Understand WHY behind TEA principles"
+    description: "Risk-based testing, DoD, testing as engineering philosophy"
+    recommended_for:
+      - beginner
+      - intermediate
+    prerequisites: []
+
+  - id: session-03-architecture
+    name: "Architecture & Patterns"
+    duration: "60 min"
+    difficulty: intermediate
+    objective: "Understand TEA patterns and architecture"
+    description: "Fixtures, network-first patterns, data factories, step-file architecture"
+    recommended_for:
+      - intermediate
+      - experienced
+    prerequisites:
+      - session-02-concepts
+
+  - id: session-04-test-design
+    name: "Test Design"
+    duration: "60 min"
+    difficulty: intermediate
+    objective: "Learn risk assessment and coverage planning"
+    description: "Test Design workflow, risk/testability assessment, coverage planning"
+    recommended_for:
+      - intermediate
+      - experienced
+    prerequisites:
+      - session-02-concepts
+
+  - id: session-05-atdd-automate
+    name: "ATDD & Automate"
+    duration: "60 min"
+    difficulty: intermediate
+    objective: "Generate tests with TDD red-green approach"
+    description: "ATDD workflow (red phase), Automate workflow, component TDD, API testing"
+    recommended_for:
+      - intermediate
+      - experienced
+    prerequisites:
+      - session-02-concepts
+
+  - id: session-06-quality-trace
+    name: "Quality & Trace"
+    duration: "45 min"
+    difficulty: intermediate
+    objective: "Audit quality and ensure traceability"
+    description: "Test Review (5 dimensions), Trace workflow, quality metrics"
+    recommended_for:
+      - intermediate
+      - experienced
+    prerequisites:
+      - session-02-concepts
+
+  - id: session-07-advanced
+    name: "Advanced Patterns"
+    duration: "ongoing"
+    difficulty: advanced
+    objective: "Deep-dive into specific knowledge fragments"
+    description: "Menu-driven exploration of 35 knowledge fragments organized by category"
+    recommended_for:
+      - experienced
+    prerequisites: []
+
+# Learning Paths by Experience Level
+learning_paths:
+  beginner:
+    recommended_sequence:
+      - session-01-quickstart
+      - session-02-concepts
+      - session-03-architecture
+      - session-04-test-design
+      - session-05-atdd-automate
+      - session-06-quality-trace
+      - session-07-advanced
+    skip_optional: []
+
+  intermediate:
+    recommended_sequence:
+      - session-01-quickstart
+      - session-02-concepts
+      - session-03-architecture
+      - session-04-test-design
+      - session-05-atdd-automate
+      - session-06-quality-trace
+      - session-07-advanced
+    skip_optional:
+      - session-01-quickstart # Can skip if already familiar
+    certificate_eligible_if_skipped: false
+
+  experienced:
+    recommended_sequence:
+      - session-02-concepts
+      - session-03-architecture
+      - session-04-test-design
+      - session-05-atdd-automate
+      - session-06-quality-trace
+      - session-07-advanced
+    skip_optional:
+      - session-01-quickstart
+    certificate_eligible_if_skipped: false
+
+# Completion Requirements
+completion:
+  minimum_sessions: 7 # All sessions required for certificate
+  passing_score: 70 # Minimum quiz score to pass session
+  average_score_threshold: 70 # Minimum average for certificate
+  certificate_note: "Certificate eligibility requires completion.minimum_sessions. If intermediate.skip_optional or experienced.skip_optional sessions are skipped, certificate eligibility is forfeited."

package/_bmad/tea/workflows/testarch/bmad-teach-me-testing/data/quiz-questions.yaml

@@ -0,0 +1,206 @@
+# Quiz Questions Bank
+# Organized by session with questions, answers, and explanations
+
+session-01-quickstart:
+  passing_score: 70
+  questions:
+    - id: q1-purpose
+      question: "What is the primary purpose of TEA?"
+      options:
+        A: "Replace all testing tools with a single framework"
+        B: "Make testing expertise accessible through structured workflows and knowledge"
+        C: "Automate 100% of test writing"
+        D: "Only works for Playwright tests"
+      correct: B
+      explanation: "TEA makes testing expertise accessible and scalable through workflows and knowledge fragments. It's not about replacing tools or automating everything."
+
+    - id: q2-risk-matrix
+      question: "What does the P0-P3 risk matrix help with?"
+      options:
+        A: "Prioritizing test coverage based on criticality"
+        B: "Grading test code quality"
+        C: "Measuring test execution speed"
+        D: "Tracking bug severity"
+      correct: A
+      explanation: "P0-P3 helps prioritize what to test based on risk (Probability × Impact). P0 = critical features like login, P3 = nice-to-have like tooltips."
+
+    - id: q3-engagement
+      question: "Which TEA engagement model is best for quick value in 30 minutes?"
+      options:
+        A: "TEA Enterprise"
+        B: "TEA Lite"
+        C: "TEA Integrated"
+        D: "TEA Brownfield"
+      correct: B
+      explanation: "TEA Lite is the 30-minute quick start approach. Enterprise and Integrated are more comprehensive."
+
+session-02-concepts:
+  passing_score: 70
+  questions:
+    - id: q1-p0-priority
+      question: "In the P0-P3 matrix, what priority level should login/authentication have?"
+      options:
+        A: "P3 - Low priority"
+        B: "P2 - Medium priority"
+        C: "P1 - High priority"
+        D: "P0 - Critical priority"
+      correct: D
+      explanation: "Login/authentication is P0 - critical. Business fails if broken. High usage, high impact, business-critical."
+
+    - id: q2-hard-waits
+      question: "What is the problem with using sleep(5000) instead of waitFor conditions?"
+      options:
+        A: "It makes tests slower"
+        B: "It's a hard wait that doesn't react to state changes (violates DoD)"
+        C: "It uses too much memory"
+        D: "It's not supported in modern frameworks"
+      correct: B
+      explanation: "Hard waits don't react to state changes - they guess timing. Use waitFor to react to conditions. This violates TEA Definition of Done."
+
+    - id: q3-self-cleaning
+      question: "What does 'self-cleaning tests' mean in TEA Definition of Done?"
+      options:
+        A: "Tests automatically fix their own bugs"
+        B: "Tests delete/deactivate entities they create during testing"
+        C: "Tests run faster by cleaning up code"
+        D: "Tests remove old test files"
+      correct: B
+      explanation: "Self-cleaning means tests delete/deactivate entities they created. No manual cleanup required."
+
+session-03-architecture:
+  passing_score: 70
+  questions:
+    - id: q1-fixtures
+      question: "What is the main benefit of fixture composition?"
+      options:
+        A: "Faster test execution"
+        B: "DRY - define once, reuse everywhere"
+        C: "Better error messages"
+        D: "Automatic screenshot capture"
+      correct: B
+      explanation: "Fixture composition allows you to define setup once and reuse everywhere. DRY principle for test setup."
+
+    - id: q2-network-first
+      question: "Why is 'network-first' better than mocking after the action?"
+      options:
+        A: "It's faster"
+        B: "It prevents race conditions"
+        C: "It uses less memory"
+        D: "It's easier to write"
+      correct: B
+      explanation: "Setting up network interception BEFORE the action prevents race conditions. The mock is ready when the action triggers."
+
+    - id: q3-step-file
+      question: "What pattern does this teaching workflow use?"
+      options:
+        A: "Page Object Model"
+        B: "Behavior Driven Development"
+        C: "Step-File Architecture"
+        D: "Test Pyramid"
+      correct: C
+      explanation: "This workflow uses step-file architecture: micro-file design, just-in-time loading, sequential enforcement."
+
+session-04-test-design:
+  passing_score: 70
+  questions:
+    - id: q1-test-design-purpose
+      question: "What does the Test Design workflow help you do?"
+      options:
+        A: "Write tests faster"
+        B: "Plan tests BEFORE writing them"
+        C: "Run tests in parallel"
+        D: "Debug test failures"
+      correct: B
+      explanation: "Test Design workflow helps you plan tests before writing them. Design before code, like architecture before implementation."
+
+    - id: q2-risk-calculation
+      question: "How do you calculate risk?"
+      options:
+        A: "Probability + Impact"
+        B: "Probability × Impact"
+        C: "Probability - Impact"
+        D: "Probability / Impact"
+      correct: B
+      explanation: "Risk = Probability × Impact. Multiply the likelihood of failure by the impact of failure."
+
+    - id: q3-p0-coverage
+      question: "For P0 features, which test levels should you use?"
+      options:
+        A: "Only E2E tests"
+        B: "Only unit tests"
+        C: "Unit + Integration + E2E (comprehensive)"
+        D: "Manual testing only"
+      correct: C
+      explanation: "P0 features need comprehensive coverage: Unit + Integration + E2E. High confidence for critical features."
+
+session-05-atdd-automate:
+  passing_score: 70
+  questions:
+    - id: q1-red-phase
+      question: "What is the 'red' phase in TDD?"
+      options:
+        A: "Tests fail (code doesn't exist yet)"
+        B: "Tests pass"
+        C: "Code is refactored"
+        D: "Tests are deleted"
+      correct: A
+      explanation: "Red phase: Tests fail because the code doesn't exist yet. Write tests first, then implement."
+
+    - id: q2-atdd-vs-automate
+      question: "What's the difference between ATDD and Automate workflows?"
+      options:
+        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
+      explanation: "ATDD writes failing tests first (red phase), then you implement. Automate generates tests for existing code (coverage expansion)."
+
+    - id: q3-api-testing
+      question: "Why use pure API tests without a browser?"
+      options:
+        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
+      explanation: "Pure API tests are faster (no browser overhead) and test business logic directly without UI complexity."
+
+session-06-quality-trace:
+  passing_score: 70
+  questions:
+    - id: q1-five-dimensions
+      question: "What are the 5 dimensions in Test Review workflow?"
+      options:
+        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
+      explanation: "Test Review evaluates 5 dimensions: Determinism (no flakiness), Isolation (parallel-safe), Assertions (correct checks), Structure (readable/maintainable organization), Performance (speed)."
+
+    - id: q2-release-gate
+      question: "When should the Trace workflow gate decision be RED (block release)?"
+      options:
+        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
+      explanation: "RED gate when P0 gaps exist - critical requirements not tested. Don't ship if critical features lack test coverage."
+
+    - id: q3-metrics
+      question: "Which metric matters most for quality?"
+      options:
+        A: "Total line coverage %"
+        B: "Number of tests written"
+        C: "P0/P1 coverage %"
+        D: "Test file count"
+      correct: C
+      explanation: "P0/P1 coverage matters most - it measures coverage of critical/high-priority features. Total line coverage is a vanity metric."
+
+session-07-advanced:
+  # No quiz - exploratory session
+  # Score: 100 (completion based, not quiz based)
+  passing_score: 100
+  questions: []

package/_bmad/tea/workflows/testarch/bmad-teach-me-testing/data/role-paths.yaml

@@ -0,0 +1,136 @@
+# Role-Based Content Customization
+# Defines how teaching examples and focus areas adapt based on learner role
+
+roles:
+  qa:
+    display_name: "QA Engineer"
+    focus_areas:
+      - Practical testing workflow usage
+      - Test framework setup and maintenance
+      - Test quality and coverage metrics
+      - CI/CD integration
+    example_contexts:
+      - "Expanding test coverage for existing features"
+      - "Setting up test framework for new project"
+      - "Reducing flaky tests in CI pipeline"
+      - "Improving test execution speed"
+    recommended_sessions:
+      - session-01-quickstart
+      - session-02-concepts
+      - session-03-architecture
+      - session-05-atdd-automate
+      - session-06-quality-trace
+    teaching_adaptations:
+      session-01-quickstart: "Focus on Automate workflow - quickly expand coverage"
+      session-02-concepts: "Emphasize P0-P3 for defending coverage decisions"
+      session-03-architecture: "Fixture patterns for maintainable test suites"
+      session-04-test-design: "Test design for planning coverage expansion"
+      session-05-atdd-automate: "ATDD and Automate for test generation"
+      session-06-quality-trace: "Test Review for quality metrics reporting"
+      session-07-advanced: "Playwright Utils for advanced testing patterns"
+
+  dev:
+    display_name: "Software Developer"
+    focus_areas:
+      - Integration testing perspective
+      - TDD approach
+      - Test-driven development workflow
+      - Unit and integration tests
+    example_contexts:
+      - "Writing tests alongside feature development"
+      - "Using ATDD to drive implementation"
+      - "Integrating tests into development workflow"
+      - "Testing APIs and business logic"
+    recommended_sessions:
+      - session-01-quickstart
+      - session-02-concepts
+      - session-05-atdd-automate
+      - session-03-architecture
+      - session-04-test-design
+    teaching_adaptations:
+      session-01-quickstart: "Focus on ATDD - tests drive implementation"
+      session-02-concepts: "Connect DoD to code quality standards"
+      session-03-architecture: "Fixtures as code patterns, like dependency injection"
+      session-04-test-design: "Risk assessment before writing code"
+      session-05-atdd-automate: "Red-green-refactor TDD cycle"
+      session-06-quality-trace: "Test quality like code quality - refactoring applies"
+      session-07-advanced: "API testing patterns, component TDD"
+
+  lead:
+    display_name: "Tech Lead / Engineering Manager"
+    focus_areas:
+      - Test architecture decisions
+      - Team testing patterns
+      - Framework and tooling choices
+      - Quality standards enforcement
+    example_contexts:
+      - "Establishing team testing standards"
+      - "Choosing test architecture patterns"
+      - "Code review for test quality"
+      - "Scaling test automation across team"
+    recommended_sessions:
+      - session-01-quickstart
+      - session-03-architecture
+      - session-04-test-design
+      - session-06-quality-trace
+      - session-07-advanced
+    teaching_adaptations:
+      session-01-quickstart: "TEA as team standard - scalable patterns"
+      session-02-concepts: "DoD as code review checklist - enforce quality"
+      session-03-architecture: "Architecture patterns for team consistency"
+      session-04-test-design: "Test design as planning phase in development"
+      session-05-atdd-automate: "ATDD for team TDD adoption"
+      session-06-quality-trace: "Test Review for quality metrics and team standards"
+      session-07-advanced: "Step-file architecture, fixture patterns, CI governance"
+
+  vp:
+    display_name: "VP Engineering / Director"
+    focus_areas:
+      - Testing strategy and ROI
+      - Quality metrics that matter
+      - Team scalability
+      - Risk management through testing
+    example_contexts:
+      - "Justifying test automation investment"
+      - "Scaling testing across multiple teams"
+      - "Quality metrics for stakeholder reporting"
+      - "Risk mitigation through test coverage"
+    recommended_sessions:
+      - session-01-quickstart
+      - session-02-concepts
+      - session-04-test-design
+      - session-06-quality-trace
+    teaching_adaptations:
+      session-01-quickstart: "TEA scales testing without scaling headcount"
+      session-02-concepts: "Risk-based testing aligns engineering with business impact"
+      session-03-architecture: "Architecture patterns reduce maintenance costs"
+      session-04-test-design: "Test design makes risk visible to stakeholders"
+      session-05-atdd-automate: "ATDD reduces defect rates early"
+      session-06-quality-trace: "Quality metrics: P0/P1 coverage, not vanity metrics"
+      session-07-advanced: "Governance patterns, CI orchestration, NFR assessment"
+
+# Role-Based Example Types
+example_types:
+  qa:
+    - "Test suite maintenance scenarios"
+    - "Coverage expansion projects"
+    - "Flaky test debugging"
+    - "CI pipeline configuration"
+
+  dev:
+    - "Feature development with TDD"
+    - "API integration testing"
+    - "Unit test patterns"
+    - "Mocking and stubbing"
+
+  lead:
+    - "Team architecture decisions"
+    - "Code review scenarios"
+    - "Standard enforcement"
+    - "Tooling selection"
+
+  vp:
+    - "ROI calculations"
+    - "Quality dashboards"
+    - "Risk reporting"
+    - "Team scaling strategies"