Skip to content
frontend-qa

Roadmap

This mirrors docs/ROADMAP.md in the repository. Update both together. Status reflects the actual state of the code, not intentions.

Available today

Section titled “Available today”
  • Phase 2 — Browser engine. Multi-route scans, same-origin route discovery, HAR capture, configurable viewport, event-driven quiescence wait, dev-server reuse/auto-launch.
  • Phase 3 — QA engines. Accessibility (--a11y, axe-core), performance (--perf, Lighthouse over CDP), visual regression (--visual, pixelmatch against a stored baseline), bundle analysis (bundle subcommand).
  • Phase 4 — Code intelligence. static subcommand: ts-morph analysis for missing alt, unsafe dangerouslySetInnerHTML, dead exports, unresolved imports, TODO/FIXME. Cross-links to runtime issues via source/element, no separate schema.
  • Phase 5 — MCP server. Five stdio tools (run_scan/get_report/get_issues/get_console_errors/get_screenshot) over @modelcontextprotocol/sdk, dogfooded in this repo’s own .mcp.json.

In progress

Section titled “In progress”
  • Phase 6 — CI. GitHub Actions matrix (Node LTS × OS), cached Playwright browsers, integration suite on every PR, coverage threshold.

Planned

Section titled “Planned”
  • Phase 7 — Release automation. changesets or semantic-release, signed provenance (--provenance) on publish, changelog generated from conventional commits.
  • This documentation website’s own publish/deploy step — the site itself is built but not yet deployed anywhere (see Design Decisions).

Post-MVP (not committed to a phase yet)

Section titled “Post-MVP (not committed to a phase yet)”
  • Support for non-React frameworks (Vue, Svelte, plain HTML) and Cypress.
  • Storybook integration — scan every story.
  • Baseline diffing across runs for regression detection.

Future / research (ideas, not commitments)

Section titled “Future / research (ideas, not commitments)”
  • An optional local LLM reasoning layer (e.g. llama.cpp/Ollama) — strictly opt-in, behind a flag, never a default. The core report must stay LLM-free regardless of whether this ships.
  • Coverage-guided route discovery.
  • Delta reports between branches.

Anything in this last section is an idea under consideration, not a committed feature — don’t treat it as documentation of current or guaranteed behavior.