Testing Maps is a visual mind map for organizing test scenarios. Each node is a scenario with a status, type, priority, and risk level. Everything runs locally in your browser — no account, no server.
Open the workspace and click the map dropdown (top-left corner, next to the logo). Choose New Map and type a name.
To start from an existing plan, choose Import instead. Paste your markdown or use our example file:
From the same dropdown you can also Rename, Duplicate, or Delete maps.
Select any node and press Tab to create a child scenario. Double-click a label to rename it inline.
Each node is a test scenario — a single thing to verify. Group related scenarios under parent nodes to keep your map organized.
You can also use the Add Scenario button in the bottom-right toolbar.
To move a scenario to a different parent, drag it onto another node — the target highlights blue. To delete, select it and press Backspace.
Double-click any node to open the Edit panel. From there you set everything about the scenario:
Status
Test Type
Priority
Risk
The panel also has fields for Instructions (what to test), Expected Results (what should happen), and a Code Reference (link to your test file).
Here's what a fully annotated node looks like with filters on:
You can also quick-edit from the ⋯ menu on hover: Edit Name, Duplicate, or Delete.
The bottom bar has filter toggles. Click any filter to show or hide that metadata on all nodes:
Coverage bar (top-center)
Shows a real-time count of all scenarios in your map:
Green = verified. Gray = untested. Red = failed. Updates instantly as you change statuses.
Your data lives in your browser only.
Clearing browser data, switching browsers, or using incognito mode will lose your maps. Export regularly.
Press ⌘ + E to export your map to markdown. You can copy it to clipboard or download as a .md file.
Press ⌘ + I to import. Choose "Create New Map" or "Replace Current Map".
Markdown format
# My Test Plan
- **Auth Module** [UNTESTED] (manual)
- *Priority:* critical
- *Risk:* high
- **Login Flow** [VERIFIED] (e2e)
- *Instructions:* Navigate to /login
- *Expected:* Form renders
- *Code:* `e2e/auth.spec.ts`
- *Priority:* high
- **Registration** [FAILED] (unit)Each indentation level becomes a parent → child relationship. The format is human-readable and git-friendly — commit it to your repo as a backup.
Press ? in the workspace to see this list.