qa-phase2

What problem does it solve?

Phase 2: Review the existing testing plan with the knowledge gained from Phase 1 (PR diff, code changes, environment state). Generate bug hypotheses and expand the plan if needed. Never make the plan shorter — only add.

Core Features & Use Cases

• Re-read the Testing Plan: Read both {testFolder}/testing-plan.md and {testFolder}/test-cases.json to understand every test case (API and browser), its priority, and its steps.
• Load Cross-Cutting Test Strategies: Based on the change type (from Phase 1), load relevant strategies from {KNOWLEDGEBASE_PATH}/test-strategies/:
• Generate Bug Hypotheses: Think adversarially. Combine PR analysis with knowledge base including patterns in bugs/patterns.md and historical issues from platform docs.
• Expand the Testing Plan: Add new test cases to {testFolder}/test-cases.json (API tests → add to apiTests; browser tests → add to browserTests). Mark all new tests as "PENDING" and do not modify existing tests.
• Update Plan Meta & Share: Update the status in test-cases.json to PHASE2 and share the plan with the team for review.

Quick Start

Load the Phase 2 skill, review Phase 1 insights, and begin expanding the testing plan by adding new test cases.