English | 한국어
Turn a PR diff into an evidence-backed QA plan before merge.
QAMap is a local-first CLI that reads the current branch, repository structure, and existing tests. It answers three questions:
- Which behavior and user flows may be affected?
- Which normal, failure, boundary, and state-transition scenarios matter?
- Which changed files, lines, symbols, and commits support each judgment?
QAMap can then route an existing validation command or prepare optional automation. It does not upload source code or make its own LLM call.
With Node.js 20 or newer, run this from the branch you want to review:
npx --yes @ivorycanvas/qamap@latest qaThe command performs read-only static analysis. It does not change project files or run product tests. For repeat use, other package managers, and local changes, see the adoption guide.
Install the plugin when you want an agent to invoke the same local workflow during PR review or test planning.
The host agent still uses its own model and permissions. QAMap provides the local, deterministic repository analysis inside that workflow.
| Section | What it tells you |
|---|---|
| Change | Which behavior probably changed. |
| Verify before merge | Which scenarios matter before merge. |
| Evidence | Which commit and code location support the judgment. |
| Next | What can be reviewed, run, or drafted next. |
The default qa command creates a plan and remains not run. Use qamap qa run
only when you want to execute a selected repository command. Use
qamap e2e draft . --dry-run to preview optional browser, mobile, API, CLI, or
manual automation.
This public fixture changes a subscription renewal flow. QAMap finds the
duplicate-request risk, cites the changed source, and keeps execution marked
not run.
Open the exact CLI output and first-run walkthrough.
commit + diff
-> affected behavior and flow
-> risk-based QA scenarios
-> evidence for every judgment
-> existing validation or optional automationQAMap follows direct change evidence before broad repository guesses. Missing Playwright, Maestro, selectors, fixtures, or a test runner does not hide an important scenario. When evidence is insufficient, QAMap stops instead of inventing a contract or a passing result.
| Goal | Guide |
|---|---|
| Review one branch | First-run walkthrough |
| Adopt QAMap in a team | Adoption guide |
| Use QAMap from an agent | Agent integration |
| Review every command | Command reference |
| Inspect benchmark evidence | Benchmarking |
QAMap is early and pre-1.0. Static analysis cannot know every product decision,
and inferred scenarios still require review. One passing command does not prove
that an entire product passed QA.
False positives, missed risks, and unusable drafts are especially useful. Start with CONTRIBUTING.md, and never publish private repository, customer, or credential data.