qaa-agent 1.6.2 → 1.7.0

package/.mcp.json

@@ -1,8 +1,8 @@
-{
-  "mcpServers": {
-    "playwright": {
-      "command": "npx",
-      "args": ["@playwright/mcp@latest"]
-    }
-  }
-}
+{
+  "mcpServers": {
+    "playwright": {
+      "command": "npx",
+      "args": ["@playwright/mcp@latest"]
+    }
+  }
+}

package/CHANGELOG.md

@@ -1,71 +1,93 @@
-
-# Changelog
-
-All notable changes to QAA (QA Automation Agent) are documented here.
-
-## [1.6.0] - 2026-03-25
-
-### Added
-- Playwright MCP server bundled in agent package (`.mcp.json`) -- starts automatically when opening project in Claude Code
-- Persistent locator registry at `.qa-output/locators/` -- accumulates real locators across features over time
-  - Per-feature files: `{feature}.locators.md` -- extracted locators for each feature tested
-  - Central index: `LOCATOR_REGISTRY.md` -- all locators by page, searchable by any command
-- Browser-based locator extraction step in `/create-test` and `/qa-from-ticket` -- navigates live app with Playwright MCP and captures real data-testid, ARIA roles, and labels before generating tests
-- Registry cache: if locators for a feature already exist in the registry, browser extraction is skipped (reuses cached locators)
-- `--app-url` flag added to `/qa-from-ticket`
-- CHANGELOG.md
-
-### Changed
-- `qaa-executor` now reads locator registry (when available) to use real locators in POMs instead of proposing them
-- `/create-test` flow: checks registry first, then extracts via browser if needed, BEFORE test generation
-- `/qa-from-ticket` workflow: locator extraction step added after source scan, before test case generation
-
-### Removed
-- `/qa-analyze` command (deprecated since v1.4.0, fully replaced by `/qa-map`)
-
-## [1.5.0] - 2026-03-24
-
-### Added
-- Stable release
-
-## [1.4.0]
-
-### Changed
-- Merged `/qa-analyze` into `/qa-map` -- single command for codebase scanning and analysis
-- Consolidated pipeline flow
-
-### Deprecated
-- `/qa-analyze` command (use `/qa-map` instead)
-
-## [1.3.0]
-
-### Added
-- `qa-learner` skill -- persistent preferences from user corrections
-- Preferences saved to `~/.claude/qaa/MY_PREFERENCES.md`
-- Trigger detection for English and Spanish frustration signals
-
-## [1.2.0]
-
-### Added
-- `qaa-codebase-mapper` agent -- 4 parallel focus areas (testability, risk, patterns, existing tests)
-- `qaa-project-researcher` agent -- researches best testing stack and practices
-- 8 codebase map documents produced by mapper
-
-## [1.1.0]
-
-### Added
-- Workflow definitions for all pipeline stages
-- Interactive installer (`npx qaa-agent`)
-- `qaa init` command for per-project initialization
-- npm package distribution
-
-## [1.0.0]
-
-### Added
-- Full QA automation pipeline -- 11 agents, 17 commands, 10 templates, 7 workflows
-- 3 workflow options (dev-only, immature QA, mature QA)
-- 4-layer test validation (syntax, structure, dependencies, logic)
-- Page Object Model generation with CLAUDE.md standards
-- Test ID injection for frontend components
-- Bug detective failure classification
-- Draft PR delivery with branch naming convention
+
+# Changelog
+
+All notable changes to QAA (QA Automation Agent) are documented here.
+
+## [1.7.0] - 2026-04-02
+
+### Added
+- **qaa-testid-injector**: Playwright MCP integration for live DOM verification before injection, codebase map reading (CODE_PATTERNS, TEST_SURFACE, TESTABILITY), and locator registry cross-referencing
+- **qaa-validator**: codebase map reading (CODE_PATTERNS, TEST_SURFACE, API_CONTRACTS) for structure and logic validation, locator registry cross-check for POM accuracy
+- **qaa-planner**: locator registry reading to assess E2E feasibility and improve complexity estimation
+- **qaa-analyzer**: locator registry reading to inform risk assessment and testing pyramid recommendations
+- **qaa-e2e-runner**: locator registry update after execution -- all discovered real locators are persisted
+- **qa-validate workflow**: now passes codebase map and locator registry to validator agent
+- **qa-gap workflow**: now passes codebase map and locator registry to analyzer agent
+- **qa-testid workflow**: now passes codebase map, locator registry, and app_url to injector agent
+
+### Changed
+- **E2E runner max fix loops: 3 → 5** -- more attempts to fix locator/assertion mismatches before giving up
+- **Installer**: updated paths for new package structure (commands/ and skills/ at root level), updated command list to reflect 7 consolidated commands
+- **Package structure**: commands and skills now live at package root instead of `.claude/` subdirectory
+- **Repository**: moved to `capmation/qaa-testing`
+
+### Consolidated
+- 7 slash commands: `/qa-start`, `/qa-create-test`, `/qa-map`, `/qa-testid`, `/qa-pr`, `/qa-audit`, `/qa-fix`
+- Removed standalone `/qa-analyze`, `/qa-validate`, `/qa-gap` -- integrated into other commands
+
+## [1.6.0] - 2026-03-25
+
+### Added
+- Playwright MCP server bundled in agent package (`.mcp.json`) -- starts automatically when opening project in Claude Code
+- Persistent locator registry at `.qa-output/locators/` -- accumulates real locators across features over time
+  - Per-feature files: `{feature}.locators.md` -- extracted locators for each feature tested
+  - Central index: `LOCATOR_REGISTRY.md` -- all locators by page, searchable by any command
+- Browser-based locator extraction step in `/create-test` and `/qa-from-ticket` -- navigates live app with Playwright MCP and captures real data-testid, ARIA roles, and labels before generating tests
+- Registry cache: if locators for a feature already exist in the registry, browser extraction is skipped (reuses cached locators)
+- `--app-url` flag added to `/qa-from-ticket`
+- CHANGELOG.md
+
+### Changed
+- `qaa-executor` now reads locator registry (when available) to use real locators in POMs instead of proposing them
+- `/create-test` flow: checks registry first, then extracts via browser if needed, BEFORE test generation
+- `/qa-from-ticket` workflow: locator extraction step added after source scan, before test case generation
+
+### Removed
+- `/qa-analyze` command (deprecated since v1.4.0, fully replaced by `/qa-map`)
+
+## [1.5.0] - 2026-03-24
+
+### Added
+- Stable release
+
+## [1.4.0]
+
+### Changed
+- Merged `/qa-analyze` into `/qa-map` -- single command for codebase scanning and analysis
+- Consolidated pipeline flow
+
+### Deprecated
+- `/qa-analyze` command (use `/qa-map` instead)
+
+## [1.3.0]
+
+### Added
+- `qa-learner` skill -- persistent preferences from user corrections
+- Preferences saved to `~/.claude/qaa/MY_PREFERENCES.md`
+- Trigger detection for English and Spanish frustration signals
+
+## [1.2.0]
+
+### Added
+- `qaa-codebase-mapper` agent -- 4 parallel focus areas (testability, risk, patterns, existing tests)
+- `qaa-project-researcher` agent -- researches best testing stack and practices
+- 8 codebase map documents produced by mapper
+
+## [1.1.0]
+
+### Added
+- Workflow definitions for all pipeline stages
+- Interactive installer (`npx qaa-agent`)
+- `qaa init` command for per-project initialization
+- npm package distribution
+
+## [1.0.0]
+
+### Added
+- Full QA automation pipeline -- 11 agents, 17 commands, 10 templates, 7 workflows
+- 3 workflow options (dev-only, immature QA, mature QA)
+- 4-layer test validation (syntax, structure, dependencies, logic)
+- Page Object Model generation with CLAUDE.md standards
+- Test ID injection for frontend components
+- Bug detective failure classification
+- Draft PR delivery with branch naming convention