@bugzy-ai/bugzy 1.11.3 → 1.12.0

package/dist/cli/index.cjs

@@ -159,22 +159,9 @@ Read the test plan from \`test-plan.md\` to understand:
 - Identify existing Page Objects in \`./tests/pages/\`
 - Avoid creating overlapping test cases or duplicate automation`
         },
-        // Step 6: Documentation Researcher (conditional inline)
+        // Step 6: Documentation Researcher (conditional library step)
         {
-          inline: true,
-          title: "Gather Product Documentation",
-          content: `{{INVOKE_DOCUMENTATION_RESEARCHER}} to gather comprehensive product documentation:
-
-\`\`\`
-Explore all available product documentation, specifically focusing on:
-- UI elements and workflows
-- User interactions and navigation paths
-- Form fields and validation rules
-- Error messages and edge cases
-- Authentication and authorization flows
-- Business rules and constraints
-- API endpoints for test data setup
-\`\`\``,
+          stepId: "gather-documentation",
           conditionalOnSubagent: "documentation-researcher"
         },
         // Step 7: Exploration Protocol (from library)
@@ -460,33 +447,9 @@ var init_generate_test_plan = __esm({
           title: "Initialize Environment Variables Tracking",
           content: `Create a list to track all TEST_ prefixed environment variables discovered throughout the process.`
         },
-        // Step 8: Documentation Researcher (conditional inline)
+        // Step 8: Documentation Researcher (conditional library step)
         {
-          inline: true,
-          title: "Gather Comprehensive Project Documentation",
-          content: `{{INVOKE_DOCUMENTATION_RESEARCHER}} to explore and gather all available project information and other documentation sources. This ensures the test plan is based on complete and current information.
-
-\`\`\`
-Explore all available project documentation related to: $ARGUMENTS
-
-Specifically gather:
-- Product specifications and requirements
-- User stories and acceptance criteria
-- Technical architecture documentation
-- API documentation and endpoints
-- User roles and permissions
-- Business rules and validations
-- UI/UX specifications
-- Known limitations or constraints
-- Existing test documentation
-- Bug reports or known issues
-\`\`\`
-
-The agent will:
-1. Check its memory for previously discovered documentation
-2. Explore workspace for relevant pages and databases
-3. Build a comprehensive understanding of the product
-4. Return synthesized information about all discovered documentation`,
+          stepId: "gather-documentation",
           conditionalOnSubagent: "documentation-researcher"
         },
         // Step 9: Exploration Protocol (from library)
@@ -966,6 +929,7 @@ Based on the event source, load the handler from \`.bugzy/runtime/handlers/\`:
 
 **Step 1: Detect Event Source from Payload:**
 - \`com.jira-server.*\` event type prefix -> \`.bugzy/runtime/handlers/jira.md\`
+- \`com.recall.*\` event type prefix -> \`.bugzy/runtime/handlers/recall.md\`
 - \`github.*\` or GitHub webhook structure -> \`.bugzy/runtime/handlers/github.md\`
 - \`linear.*\` or Linear webhook -> \`.bugzy/runtime/handlers/linear.md\`
 - Other sources -> Check for matching handler file by source name
@@ -1033,19 +997,9 @@ Based on event type and content, generate 3-5 specific search queries:
 - Find relevant documentation
 - Check for known issues`
         },
-        // Step 9: Documentation Research (conditional inline)
+        // Step 9: Documentation Research (conditional library step)
         {
-          inline: true,
-          title: "Use Documentation Researcher",
-          content: `#### 3.3 Use Documentation Researcher if Needed
-
-{{INVOKE_DOCUMENTATION_RESEARCHER}} to find information about unknown features or components:
-
-For events mentioning unknown features or components, ask the agent to explore project documentation and return:
-- Feature specifications
-- Related test cases
-- Known issues or limitations
-- Component dependencies`,
+          stepId: "gather-documentation",
           conditionalOnSubagent: "documentation-researcher"
         },
         // Step 10: Task Planning (inline)
@@ -1223,7 +1177,7 @@ Create files if they don't exist:
       ],
       requiredSubagents: ["team-communicator"],
       optionalSubagents: ["documentation-researcher", "issue-tracker"],
-      dependentTasks: ["verify-changes"]
+      dependentTasks: ["verify-changes", "generate-test-cases", "run-tests"]
     };
   }
 });
@@ -1658,6 +1612,42 @@ Generate summary of test selection based on description analysis:
 - **Execution strategy**: [smart selection | full suite | smoke tests | user-specified]
 \`\`\``
         },
+        // Step 7b: Create Tests for Coverage Gaps (conditional - test-code-generator)
+        {
+          inline: true,
+          title: "Create Tests for Coverage Gaps",
+          content: `If the test scope analysis found that existing tests do NOT cover the changed feature:
+
+### Identify Coverage Gaps
+
+Compare:
+- **Changed feature**: What the Jira issue / PR describes
+- **Existing tests**: What test specs already exist in tests/specs/
+
+If there are NO automated tests covering the new/changed feature:
+
+### Create Manual Test Cases
+
+Create or update test case files in \`./test-cases/\` for the new feature:
+- One file per test scenario (e.g., \`test-cases/TC-XXX-checkout-improved.md\`)
+- Include: objective, preconditions, test steps, expected results
+- Mark \`automated: true\` for scenarios that should be automated
+
+### Generate Playwright Specs
+
+{{INVOKE_TEST_CODE_GENERATOR}} to create automated test specs:
+- Read the manual test cases you just created
+- Explore the feature in the browser to discover selectors and flows
+- Create Page Objects in \`./tests/pages/\` if needed
+- Create test specs in \`./tests/specs/\` matching the test cases
+- Run each new test to verify it passes
+- Update the manual test case with \`automated_test\` reference
+
+### If Tests Already Cover the Feature
+
+Skip this step \u2014 proceed directly to running existing tests.`,
+          conditionalOnSubagent: "test-code-generator"
+        },
         // Step 8-11: Test Execution (library steps)
         "run-playwright-tests",
         "parse-test-results",
@@ -1764,38 +1754,26 @@ All user-facing changes are fully covered by automated tests.
 [Safe to merge | Review bugs before merging | Do not merge]
 \`\`\``
         },
-        // Step 15: Documentation Research (conditional inline)
+        // Step 14b: Post Results to Slack (conditional on team-communicator)
         {
           inline: true,
-          title: "Understanding the Change (Documentation Research)",
-          content: `{{INVOKE_DOCUMENTATION_RESEARCHER}} to gather comprehensive context about the changed features:
-
-Explore project documentation related to the changes.
-
-Specifically gather:
-- Product specifications for affected features
-- User stories and acceptance criteria
-- Technical architecture documentation
-- API endpoints and contracts
-- User roles and permissions relevant to the change
-- Business rules and validations
-- UI/UX specifications
-- Known limitations or constraints
-- Related bug reports or known issues
-- Existing test documentation for this area
-
-The agent will:
-1. Check its memory for previously discovered documentation
-2. Explore workspace for relevant pages and databases
-3. Build comprehensive understanding of the affected features
-4. Return synthesized information to inform testing strategy
-
-Use this information to:
-- Better understand the change context
-- Identify comprehensive test scenarios
-- Recognize integration points and dependencies
-- Spot potential edge cases or risk areas
-- Enhance manual verification checklist generation`,
+          title: "Post Results to Team Channel",
+          content: `**IMPORTANT \u2014 Do this NOW before proceeding to any other step.**
+
+{{INVOKE_TEAM_COMMUNICATOR}} to post the verification results summary to the team Slack channel.
+
+Include in the message:
+- What was verified (issue ID and feature name)
+- Test results (total / passed / failed)
+- New tests created (list file names)
+- Manual verification items count
+- Overall recommendation (safe to merge / review / block)
+- Any blocking issues or critical findings`,
+          conditionalOnSubagent: "team-communicator"
+        },
+        // Step 15: Documentation Research (conditional library step)
+        {
+          stepId: "gather-documentation",
           conditionalOnSubagent: "documentation-researcher"
         },
         // Step 16: Report Results (inline)
@@ -1891,7 +1869,7 @@ A successful verification includes:
         }
       ],
       requiredSubagents: ["test-runner", "test-debugger-fixer"],
-      optionalSubagents: ["documentation-researcher", "issue-tracker", "team-communicator", "changelog-historian"],
+      optionalSubagents: ["documentation-researcher", "issue-tracker", "team-communicator", "changelog-historian", "test-code-generator"],
       dependentTasks: []
     };
   }
@@ -1938,6 +1916,10 @@ This command orchestrates the complete test coverage workflow in a single execut
         // Phase 1: Setup
         "load-project-context",
         "read-knowledge-base",
+        {
+          stepId: "gather-documentation",
+          conditionalOnSubagent: "documentation-researcher"
+        },
         // Phase 2: Exploration Protocol
         "exploration-protocol",
         // Execute exploration via test-runner
@@ -6507,6 +6489,40 @@ The \`.env\` file access is blocked by settings.json.`,
   tags: ["security", "required"]
 };
 
+// src/tasks/steps/setup/gather-documentation.ts
+init_cjs_shims();
+var gatherDocumentationStep = {
+  id: "gather-documentation",
+  title: "Gather Project Documentation",
+  category: "setup",
+  content: `## Gather Project Documentation
+
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to explore and gather all available project information.
+
+Specifically gather:
+- Product specifications and requirements
+- User stories and acceptance criteria
+- Technical architecture documentation
+- API documentation and endpoints
+- User roles and permissions
+- Business rules and validations
+- UI/UX specifications
+- Known limitations or constraints
+- Existing test documentation
+- Bug reports or known issues
+
+The agent will:
+1. Check its memory for previously discovered documentation
+2. Explore workspace for relevant pages and databases
+3. Build comprehensive understanding of the product
+4. Return synthesized information about all discovered documentation
+
+Use this information to inform testing strategy and identify comprehensive scenarios.`,
+  requiresSubagent: "documentation-researcher",
+  invokesSubagents: ["documentation-researcher"],
+  tags: ["setup", "context", "documentation"]
+};
+
 // src/tasks/steps/exploration/exploration-protocol.ts
 init_cjs_shims();
 var explorationProtocolStep = {
@@ -7767,6 +7783,7 @@ var STEP_LIBRARY = {
   "read-knowledge-base": readKnowledgeBaseStep,
   "read-test-strategy": readTestStrategyStep,
   "load-project-context": loadProjectContextStep,
+  "gather-documentation": gatherDocumentationStep,
   // Exploration
   "exploration-protocol": explorationProtocolStep,
   // Clarification