@bugzy-ai/bugzy 1.14.0 → 1.15.0

package/dist/tasks/index.js

@@ -24,9 +24,9 @@ var TASK_SLUGS = {
 var generateTestCasesTask = {
   slug: TASK_SLUGS.GENERATE_TEST_CASES,
   name: "Generate Test Cases",
-  description: "Generate manual test case documentation AND automated Playwright test scripts from test plan",
+  description: "Generate manual test case documentation AND automated test scripts from test plan",
   frontmatter: {
-    description: "Generate manual test case documentation AND automated Playwright test scripts from test plan",
+    description: "Generate manual test case documentation AND automated test scripts from test plan",
     "argument-hint": "--type [exploratory|functional|regression|smoke] --focus [optional-feature]"
   },
   steps: [
@@ -34,12 +34,12 @@ var generateTestCasesTask = {
     {
       inline: true,
       title: "Generate Test Cases Overview",
-      content: `Generate comprehensive test artifacts including BOTH manual test case documentation AND automated Playwright test scripts.
+      content: `Generate comprehensive test artifacts including BOTH manual test case documentation AND automated test scripts. Read \`./tests/CLAUDE.md\` for framework-specific conventions, directory structure, and commands.
 
 This command generates:
 1. **Manual Test Case Documentation** (in \`./test-cases/\`) - Human-readable test cases in markdown format
-2. **Automated Playwright Tests** (in \`./tests/specs/\`) - Executable TypeScript test scripts
-3. **Page Object Models** (in \`./tests/pages/\`) - Reusable page classes for automated tests
+2. **Automated Test Scripts** (in directory from \`./tests/CLAUDE.md\`) - Executable test scripts
+3. **Page Objects** (in directory from \`./tests/CLAUDE.md\`) - Reusable page classes for automated tests
 4. **Supporting Files** (fixtures, helpers, components) - As needed for test automation`
     },
     // Step 2: Security Notice (library)
@@ -74,9 +74,9 @@ Read the test plan from \`test-plan.md\` to understand:
 
 **1.2 Check Existing Test Cases and Tests**
 - List all files in \`./test-cases/\` to understand existing manual test coverage
-- List all files in \`./tests/specs/\` to understand existing automated tests
+- List existing automated tests in the test directory (see \`./tests/CLAUDE.md\` for structure)
 - Determine next test case ID (TC-XXX format)
-- Identify existing Page Objects in \`./tests/pages/\`
+- Identify existing page objects (see \`./tests/CLAUDE.md\` for directory)
 - Avoid creating overlapping test cases or duplicate automation`
     },
     // Step 6: Documentation Researcher (conditional library step)
@@ -185,8 +185,8 @@ Before invoking the agent, identify the test cases for the current area:
 - Test type: {type}
 - Test plan: test-plan.md
 - Manual test cases directory: ./test-cases/
-- Existing automated tests: ./tests/specs/
-- Existing Page Objects: ./tests/pages/
+- Existing automated tests: [directory from ./tests/CLAUDE.md]
+- Existing page objects: [directory from ./tests/CLAUDE.md]
 
 **Knowledge Base Patterns (MUST APPLY):**
 Include ALL relevant testing patterns from the knowledge base that apply to this area. For example, if the KB documents timing behaviors (animation delays, loading states), selector gotchas, or recommended assertion approaches \u2014 list them here explicitly and instruct the agent to use the specific patterns described (e.g., specific assertion methods with specific timeouts). The test-code-generator does not have access to the knowledge base, so you MUST relay the exact patterns and recommended code approaches.
@@ -197,7 +197,7 @@ Include ALL relevant testing patterns from the knowledge base that apply to this
 3. Explore the feature area to understand implementation (gather selectors, URLs, flows)
 4. Build missing Page Objects and supporting code
 5. For each test case marked \`automated: true\`:
-   - Create automated Playwright test in ./tests/specs/
+   - Create automated test in the test directory (from ./tests/CLAUDE.md)
    - Update the manual test case file to reference the automated test path
    - Apply ALL knowledge base patterns listed above (timing, selectors, assertions)
 6. Run and iterate on each test until it passes or fails with a product bug
@@ -228,15 +228,7 @@ Move to the next area and repeat until all areas are complete.
     {
       inline: true,
       title: "Create Directories if Needed",
-      content: `Ensure required directories exist:
-\`\`\`bash
-mkdir -p ./test-cases
-mkdir -p ./tests/specs
-mkdir -p ./tests/pages
-mkdir -p ./tests/components
-mkdir -p ./tests/fixtures
-mkdir -p ./tests/helpers
-\`\`\``
+      content: `Ensure required directories exist. Create the \`./test-cases/\` directory for manual test cases, and create the test directories specified in \`./tests/CLAUDE.md\` (test specs, page objects, components, fixtures, helpers).`
     },
     // Step 14: Extract Env Variables (library)
     "extract-env-variables",
@@ -256,7 +248,7 @@ mkdir -p ./tests/helpers
    - Features covered by automation
    - Areas kept manual-only (and why)
 3. Highlight key automated test scenarios
-4. Share command to run automated tests: npx playwright test
+4. Share command to run automated tests (from \`./tests/CLAUDE.md\`)
 5. Ask for team review and validation
 6. Mention any areas needing exploration or clarification
 7. Use appropriate channel and threading for the update
@@ -301,8 +293,8 @@ The team communication should include:
 - Areas kept manual-only (and why)
 
 **Next Steps:**
-- Command to run automated tests: \`npx playwright test\`
-- Instructions to run specific test file
+- Command to run automated tests (from \`./tests/CLAUDE.md\`)
+- Instructions to run specific test file (from \`./tests/CLAUDE.md\`)
 - Note about copying .env.testdata to .env
 - Mention any exploration needed for edge cases
 
@@ -318,7 +310,7 @@ The team communication should include:
 - **Test Independence**: Each test must be runnable in isolation and in parallel`
     }
   ],
-  requiredSubagents: ["test-runner", "test-code-generator"],
+  requiredSubagents: ["browser-automation", "test-code-generator"],
   optionalSubagents: ["documentation-researcher", "team-communicator"],
   dependentTasks: []
 };
@@ -517,7 +509,7 @@ The team communication should include:
 - Instructions for the user to fill in actual values in .env.testdata before running tests`
     }
   ],
-  requiredSubagents: ["test-runner"],
+  requiredSubagents: ["browser-automation"],
   optionalSubagents: ["documentation-researcher", "team-communicator"],
   dependentTasks: []
 };
@@ -601,7 +593,28 @@ The handler file contains all necessary processing logic for the detected intent
 - Response guidelines
 - Memory update instructions`
     },
-    // Step 6: Clarification Protocol (for ambiguous intents)
+    // Step 6: Post Response via Team Communicator
+    {
+      inline: true,
+      title: "Post Response to Team",
+      content: `## Post Response to the Team
+
+After processing the message through the handler and composing your response:
+
+{{INVOKE_TEAM_COMMUNICATOR}} to post the response back to the team.
+
+**Context to include in the delegation:**
+- The original message/question from the team member
+- Your composed response with all gathered data
+- Whether this should be a thread reply (if the original message was in a thread) or a new message
+- The relevant channel (from project-context.md)
+
+**Do NOT:**
+- Skip posting and just display the response as text output
+- Ask the user whether to post \u2014 the message came from the team, the response goes back to the team
+- Compose a draft without sending it`
+    },
+    // Step 7: Clarification Protocol (for ambiguous intents)
     "clarification-protocol",
     // Step 8: Knowledge Base Update (library)
     "update-knowledge-base",
@@ -1018,7 +1031,7 @@ After queuing and notifying, the task is DONE. Do NOT:
 - Execute /verify-changes, /run-tests, /generate-test-cases directly
 - Wait for team response (messaging infrastructure handles that)
 - Create or modify test files
-- Run Playwright tests
+- Run automated tests
 
 #### 5.6 Update Event Processor Memory
 If new patterns discovered, append to \`.bugzy/runtime/memory/event-processor.md\`:
@@ -1125,10 +1138,10 @@ Create files if they don't exist:
 var runTestsTask = {
   slug: TASK_SLUGS.RUN_TESTS,
   name: "Run Tests",
-  description: "Execute automated Playwright tests, analyze failures, and fix test issues automatically",
+  description: "Execute automated tests, analyze failures, and fix test issues automatically",
   frontmatter: {
-    description: "Execute automated Playwright tests, analyze failures, and fix test issues automatically",
-    "argument-hint": '[file-pattern|tag|all] (e.g., "auth", "@smoke", "tests/specs/login.spec.ts")'
+    description: "Execute automated tests, analyze failures, and fix test issues automatically",
+    "argument-hint": '[file-pattern|tag|all] (e.g., "auth", "@smoke", or a specific test file path)'
   },
   steps: [
     // Step 1: Overview (inline)
@@ -1137,7 +1150,7 @@ var runTestsTask = {
       title: "Run Tests Overview",
       content: `# Run Tests Command
 
-Execute automated Playwright tests, analyze failures using JSON reports, automatically fix test issues, and log product bugs.`
+Execute automated tests, analyze failures using JSON reports, automatically fix test issues, and log product bugs. Read \`./tests/CLAUDE.md\` for framework-specific conventions and commands.`
     },
     // Step 2: Security Notice (library)
     "security-notice",
@@ -1150,9 +1163,9 @@ Execute automated Playwright tests, analyze failures using JSON reports, automat
 **Parse Arguments:**
 Extract the following from arguments:
 - **selector**: Test selection criteria
-  - File pattern: "auth" \u2192 finds tests/specs/**/*auth*.spec.ts
-  - Tag: "@smoke" \u2192 runs tests with @smoke annotation
-  - Specific file: "tests/specs/login.spec.ts"
+  - File pattern: "auth" \u2192 find matching test files (see \`./tests/CLAUDE.md\` for directory structure)
+  - Tag: "@smoke" \u2192 runs tests with tag annotation
+  - Specific file: path to a specific test file
   - All tests: "all" or "" \u2192 runs entire test suite`
     },
     // Step 4: Load Project Context (library)
@@ -1168,34 +1181,26 @@ Extract the following from arguments:
       inline: true,
       title: "Identify Automated Tests to Run",
       content: `#### Understand Test Selection
+
+Read \`./tests/CLAUDE.md\` for the test directory structure, file patterns, and execution commands.
+
 Parse the selector argument to determine which tests to run:
 
 **File Pattern** (e.g., "auth", "login"):
-- Find matching test files: \`tests/specs/**/*[pattern]*.spec.ts\`
+- Find matching test files in the test directory specified by \`./tests/CLAUDE.md\`
 - Example: "auth" \u2192 finds all test files with "auth" in the name
 
 **Tag** (e.g., "@smoke", "@regression"):
-- Run tests with specific Playwright tag annotation
-- Use Playwright's \`--grep\` option
+- Run tests with specific tag annotation using the tag command from \`./tests/CLAUDE.md\`
 
-**Specific File** (e.g., "tests/specs/auth/login.spec.ts"):
-- Run that specific test file
+**Specific File**:
+- Run that specific test file using the single-file command from \`./tests/CLAUDE.md\`
 
 **All Tests** ("all" or no selector):
-- Run entire test suite: \`tests/specs/**/*.spec.ts\`
+- Run entire test suite using the run-all command from \`./tests/CLAUDE.md\`
 
 #### Find Matching Test Files
-Use glob patterns to find test files:
-\`\`\`bash
-# For file pattern
-ls tests/specs/**/*[pattern]*.spec.ts
-
-# For specific file
-ls tests/specs/auth/login.spec.ts
-
-# For all tests
-ls tests/specs/**/*.spec.ts
-\`\`\`
+Use glob patterns to find test files in the directory structure defined by \`./tests/CLAUDE.md\`.
 
 #### Validate Test Files Exist
 Check that at least one test file was found:
@@ -1209,7 +1214,7 @@ Before running tests, confirm the selection with the user if ambiguous:
 - **No selector** (all tests): Confirm running full suite before executing`
     },
     // Step 7-10: Test Execution (library steps)
-    "run-playwright-tests",
+    "run-tests",
     "parse-test-results",
     "triage-failures",
     "fix-test-issues",
@@ -1235,8 +1240,8 @@ If no test cases match the selection criteria:
 2. List available test cases or suggest running \`/generate-test-cases\` first
 3. Provide examples of valid selection criteria
 
-#### If Test Runner Agent Fails
-If the test-runner agent encounters issues:
+#### If Browser Automation Agent Fails
+If the browser-automation agent encounters issues:
 1. Report the specific error
 2. Suggest troubleshooting steps
 3. Offer to run tests individually if batch execution failed
@@ -1250,18 +1255,18 @@ If selected test cases have formatting issues:
 ### Important Notes
 
 **Test Selection Strategy**:
-- **Always read** \`.bugzy/runtime/test-execution-strategy.md\` before selecting tests
+- **Always read** \`./tests/docs/test-execution-strategy.md\` before selecting tests
 - Default to \`@smoke\` tests for fast validation unless user explicitly requests otherwise
 - Smoke tests provide 100% manual test case coverage with zero redundancy (~2-5 min)
 - Full regression includes intentional redundancy for diagnostic value (~10-15 min)
 - Use context keywords from user request to choose appropriate tier
 
 **Test Execution**:
-- Automated Playwright tests are executed via bash command, not through agents
+- Automated tests are executed via bash command, not through agents
 - Test execution time varies by tier (see strategy document for details)
 - JSON reports provide structured test results for analysis
-- Playwright automatically captures traces, screenshots, and videos on failures
-- Test artifacts are stored in test-results/ directory
+- Test framework may capture traces, screenshots, and videos on failures (see \`./tests/CLAUDE.md\`)
+- Test artifacts are stored as defined in \`./tests/CLAUDE.md\`
 
 **Failure Handling**:
 - Test failures are automatically triaged (product bugs vs test issues)
@@ -1271,11 +1276,11 @@ If selected test cases have formatting issues:
 - Critical failures trigger immediate team notification
 
 **Related Documentation**:
-- \`.bugzy/runtime/test-execution-strategy.md\` - When and why to run specific tests
-- \`.bugzy/runtime/testing-best-practices.md\` - How to write tests (patterns and anti-patterns)`
+- \`./tests/docs/test-execution-strategy.md\` - When and why to run specific tests
+- \`./tests/docs/testing-best-practices.md\` - How to write tests (patterns and anti-patterns)`
     }
   ],
-  requiredSubagents: ["test-runner", "test-debugger-fixer"],
+  requiredSubagents: ["browser-automation", "test-debugger-fixer"],
   optionalSubagents: ["issue-tracker", "team-communicator"],
   dependentTasks: []
 };
@@ -1299,7 +1304,7 @@ var verifyChangesTask = {
 ## Overview
 
 This task performs comprehensive change verification with:
-- **Automated testing**: Execute Playwright tests with automatic triage and fixing
+- **Automated testing**: Execute automated tests with automatic triage and fixing
 - **Manual verification checklists**: Generate role-specific checklists for non-automatable scenarios
 - **Multi-trigger support**: Works from manual CLI, Slack messages, GitHub PRs, and CI/CD
 - **Smart output routing**: Results formatted and delivered to the appropriate channel`
@@ -1530,11 +1535,11 @@ Analyze the change description to identify affected feature areas:
 
 | Description Keywords | Inferred Test Scope | Example |
 |---------------------|-------------------|---------|
-| "login", "authentication", "sign in/up" | \`tests/specs/auth/\` | "Fix login page validation" -> Auth tests |
-| "checkout", "payment", "purchase" | \`tests/specs/checkout/\` | "Optimize checkout flow" -> Checkout tests |
-| "cart", "shopping cart", "add to cart" | \`tests/specs/cart/\` | "Update cart calculations" -> Cart tests |
+| "login", "authentication", "sign in/up" | Auth test suite | "Fix login page validation" -> Auth tests |
+| "checkout", "payment", "purchase" | Checkout test suite | "Optimize checkout flow" -> Checkout tests |
+| "cart", "shopping cart", "add to cart" | Cart test suite | "Update cart calculations" -> Cart tests |
 | "API", "endpoint", "backend" | API test suites | "Add new user API endpoint" -> User API tests |
-| "profile", "account", "settings" | \`tests/specs/profile/\` or \`tests/specs/settings/\` | "Profile page redesign" -> Profile tests |
+| "profile", "account", "settings" | Profile/settings test suite | "Profile page redesign" -> Profile tests |
 
 **Inference strategy:**
 1. **Extract feature keywords** from PR title and description
@@ -1609,13 +1614,13 @@ If the Jira issue or PR references test accounts/data (e.g., TEST_PREMIUM_USER,
 
 **CRITICAL**: Never conclude "manual verification required" or "BLOCKED" solely because test data is missing. Always create the test artifacts first.
 
-### Generate Playwright Specs
+### Generate Automated Test 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
+- Create page objects in the directory specified by \`./tests/CLAUDE.md\`
+- Create test specs in the directory specified by \`./tests/CLAUDE.md\`
 - Run each new test to verify it passes
 - Update the manual test case with \`automated_test\` reference
 
@@ -1625,7 +1630,7 @@ Skip this step \u2014 proceed directly to running existing tests.`,
       conditionalOnSubagent: "test-code-generator"
     },
     // Step 8-11: Test Execution (library steps)
-    "run-playwright-tests",
+    "run-tests",
     "parse-test-results",
     "triage-failures",
     "fix-test-issues",
@@ -1814,7 +1819,7 @@ Post PR comment if GitHub context available.`,
 - Recommend: Check test configuration and prerequisites
 
 **If test execution fails:**
-- Report specific error (Playwright not installed, env vars missing)
+- Report specific error (test framework not installed, env vars missing)
 - Suggest troubleshooting steps
 - Don't proceed with triage if tests didn't run
 
@@ -1844,7 +1849,7 @@ A successful verification includes:
 10. Clear recommendation provided (merge / review / block)`
     }
   ],
-  requiredSubagents: ["test-runner", "test-debugger-fixer"],
+  requiredSubagents: ["browser-automation", "test-debugger-fixer"],
   optionalSubagents: ["documentation-researcher", "issue-tracker", "team-communicator", "changelog-historian", "test-code-generator"],
   dependentTasks: []
 };
@@ -1893,7 +1898,7 @@ This command orchestrates the complete test coverage workflow in a single execut
     },
     // Phase 2: Exploration Protocol
     "exploration-protocol",
-    // Execute exploration via test-runner
+    // Execute exploration via browser-automation
     "create-exploration-test-case",
     "run-exploration",
     "process-exploration-results",
@@ -1904,7 +1909,7 @@ This command orchestrates the complete test coverage workflow in a single execut
     "generate-test-cases",
     "automate-test-cases",
     // Phase 5: Test Execution
-    "run-playwright-tests",
+    "run-tests",
     "parse-test-results",
     // Phase 6: Triage and Fix (NEW - was missing from full-test-coverage)
     "triage-failures",
@@ -1921,7 +1926,7 @@ This command orchestrates the complete test coverage workflow in a single execut
     },
     "generate-final-report"
   ],
-  requiredSubagents: ["test-runner", "test-code-generator", "test-debugger-fixer"],
+  requiredSubagents: ["browser-automation", "test-code-generator", "test-debugger-fixer"],
   optionalSubagents: ["documentation-researcher", "team-communicator", "issue-tracker"],
   dependentTasks: ["run-tests", "generate-test-cases"]
 };
@@ -1940,7 +1945,7 @@ var exploreApplicationTask = {
     {
       inline: true,
       title: "Explore Application Overview",
-      content: `Discover actual UI elements, workflows, and behaviors using the test-runner agent. Updates test plan and project documentation with findings.`
+      content: `Discover actual UI elements, workflows, and behaviors using the browser-automation agent. Updates test plan and project documentation with findings.`
     },
     // Step 2: Security Notice (from library)
     "security-notice",
@@ -1987,7 +1992,7 @@ var exploreApplicationTask = {
     "cleanup-temp-files",
     "update-knowledge-base"
   ],
-  requiredSubagents: ["test-runner"],
+  requiredSubagents: ["browser-automation"],
   optionalSubagents: ["team-communicator"],
   dependentTasks: []
 };