froid-plane-test-architecture-enterprise 1.23.4

package/src/workflows/testarch/froid-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/src/workflows/testarch/froid-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 evidence audit"
+
+# 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"

package/src/workflows/testarch/froid-teach-me-testing/data/session-content-map.yaml

@@ -0,0 +1,222 @@
+# Session Content Mapping
+# Maps each session to specific TEA documentation, knowledge fragments, and online resources
+
+base_paths:
+  tea_docs: "/docs"
+  tea_knowledge: "/src/agents/froid-tea/resources/knowledge"
+  online_base: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise"
+  github_knowledge: "https://github.com/cordya-ai/froid-plane-test-architecture-enterprise/tree/main/src/agents/froid-tea/resources/knowledge"
+
+sessions:
+  session-01-quickstart:
+    docs:
+      - path: "/docs/tutorials/tea-lite-quickstart.md"
+        title: "TEA Lite Quickstart"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/tutorials/tea-lite-quickstart/"
+      - path: "/docs/explanation/tea-overview.md"
+        title: "TEA Overview"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/tea-overview/"
+      - path: "/docs/how-to/workflows/run-automate.md"
+        title: "Run Automate Workflow"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-automate/"
+    knowledge_fragments: []
+    online_references:
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/"
+    workflows_referenced:
+      - automate
+    key_concepts:
+      - "What is TEA"
+      - "TEA Lite approach"
+      - "Engagement models"
+      - "9 workflows overview"
+
+  session-02-concepts:
+    docs:
+      - path: "/docs/explanation/testing-as-engineering.md"
+        title: "Testing as Engineering"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/testing-as-engineering/"
+      - path: "/docs/explanation/risk-based-testing.md"
+        title: "Risk-Based Testing"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/risk-based-testing/"
+      - path: "/docs/explanation/test-quality-standards.md"
+        title: "Test Quality Standards"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/test-quality-standards/"
+    knowledge_fragments:
+      - path: "/src/agents/froid-tea/resources/knowledge/test-quality.md"
+        title: "Test Quality (DoD Execution Limits)"
+      - path: "/src/agents/froid-tea/resources/knowledge/probability-impact.md"
+        title: "Probability × Impact Scoring"
+    online_references:
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/testing-as-engineering/"
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/risk-based-testing/"
+    workflows_referenced: []
+    key_concepts:
+      - "Testing as engineering philosophy"
+      - "P0-P3 risk matrix"
+      - "Probability × Impact scoring"
+      - "Definition of Done (7 principles)"
+
+  session-03-architecture:
+    docs:
+      - path: "/docs/explanation/fixture-architecture.md"
+        title: "Fixture Architecture"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/fixture-architecture/"
+      - path: "/docs/explanation/network-first-patterns.md"
+        title: "Network-First Patterns"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/network-first-patterns/"
+      - path: "/docs/explanation/step-file-architecture.md"
+        title: "Step-File Architecture"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/step-file-architecture/"
+    knowledge_fragments:
+      - path: "/src/agents/froid-tea/resources/knowledge/fixture-architecture.md"
+        title: "Fixture Architecture Patterns"
+      - path: "/src/agents/froid-tea/resources/knowledge/network-first.md"
+        title: "Network-First Implementation"
+      - path: "/src/agents/froid-tea/resources/knowledge/data-factories.md"
+        title: "Data Factories Pattern"
+    online_references:
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/explanation/fixture-architecture/"
+    workflows_referenced:
+      - framework
+    key_concepts:
+      - "Fixture composition"
+      - "Network interception patterns"
+      - "Data factory pattern"
+      - "Step-file architecture"
+
+  session-04-test-design:
+    docs:
+      - path: "/docs/how-to/workflows/run-test-design.md"
+        title: "Run Test Design Workflow"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-test-design/"
+    knowledge_fragments:
+      - path: "/src/agents/froid-tea/resources/knowledge/test-levels-framework.md"
+        title: "Test Levels Framework"
+      - path: "/src/agents/froid-tea/resources/knowledge/test-priorities-matrix.md"
+        title: "Test Priorities Matrix"
+    online_references:
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-test-design/"
+    workflows_referenced:
+      - test-design
+    key_concepts:
+      - "Test Design workflow steps"
+      - "Risk/testability assessment"
+      - "Coverage planning"
+      - "Test levels (unit/integration/E2E)"
+
+  session-05-atdd-automate:
+    docs:
+      - path: "/docs/how-to/workflows/run-atdd.md"
+        title: "Run ATDD Workflow"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-atdd/"
+      - path: "/docs/how-to/workflows/run-automate.md"
+        title: "Run Automate Workflow"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-automate/"
+    knowledge_fragments:
+      - path: "/src/agents/froid-tea/resources/knowledge/component-tdd.md"
+        title: "Component TDD Red-Green Loop"
+      - path: "/src/agents/froid-tea/resources/knowledge/api-testing-patterns.md"
+        title: "API Testing Patterns"
+      - path: "/src/agents/froid-tea/resources/knowledge/api-request.md"
+        title: "API Request Utility"
+    online_references:
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-atdd/"
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-automate/"
+    workflows_referenced:
+      - atdd
+      - automate
+    key_concepts:
+      - "ATDD workflow (red phase)"
+      - "TDD red-green-refactor"
+      - "Automate workflow (coverage expansion)"
+      - "API testing without browser"
+
+  session-06-quality-trace:
+    docs:
+      - path: "/docs/how-to/workflows/run-test-review.md"
+        title: "Run Test Review Workflow"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-test-review/"
+      - path: "/docs/how-to/workflows/run-trace.md"
+        title: "Run Trace Workflow"
+        url: "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-trace/"
+    knowledge_fragments: []
+    online_references:
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-test-review/"
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/how-to/workflows/run-trace/"
+    workflows_referenced:
+      - test-review
+      - trace
+    key_concepts:
+      - "5 dimensions of test quality"
+      - "Quality scoring (0-100)"
+      - "Requirements traceability"
+      - "Release gate decisions"
+
+  session-07-advanced:
+    docs: []
+    knowledge_fragments:
+      categories:
+        testing_patterns:
+          - fixture-architecture.md
+          - fixtures-composition.md
+          - network-first.md
+          - data-factories.md
+          - component-tdd.md
+          - api-testing-patterns.md
+          - test-healing-patterns.md
+          - selector-resilience.md
+          - timing-debugging.md
+
+        playwright_utils:
+          - overview.md
+          - library-integration-mandate.md
+          - playwright-utils-mandate.md
+          - api-request.md
+          - network-recorder.md
+          - intercept-network-call.md
+          - recurse.md
+          - log.md
+          - file-utils.md
+          - burn-in.md
+          - network-error-monitor.md
+          - contract-testing.md
+          - pactjs-utils-overview.md
+          - pactjs-utils-mandate.md
+          - pactjs-utils-consumer-helpers.md
+          - pactjs-utils-provider-verifier.md
+          - pactjs-utils-request-filter.md
+          - pact-mcp.md
+          - pact-consumer-framework-setup.md
+          - pact-consumer-di.md
+          - visual-debugging.md
+
+        browser_automation:
+          - playwright-cli.md
+
+        configuration_governance:
+          - playwright-config.md
+          - ci-burn-in.md
+          - selective-testing.md
+          - feature-flags.md
+          - risk-governance.md
+          - adr-quality-readiness-checklist.md
+
+        quality_frameworks:
+          - test-quality.md
+          - test-levels-framework.md
+          - test-priorities-matrix.md
+          - probability-impact.md
+          - nfr-criteria.md
+
+        auth_security:
+          - email-auth.md
+          - auth-session.md
+          - error-handling.md
+    online_references:
+      - "https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/reference/knowledge-base/"
+      - "https://github.com/cordya-ai/froid-plane-test-architecture-enterprise/tree/main/src/agents/froid-tea/resources/knowledge"
+    workflows_referenced: []
+    key_concepts:
+      - "Menu-driven fragment exploration"
+      - "Just-in-time deep-dive learning"
+      - "59 knowledge fragments organized by category"