jev-frontend-qa
Evidence-driven frontend QA built on Jev Ultrafast and Browser Harness, with a synthetic todo demo.
How it uses Jev
Evidence-driven frontend QA built on Jev Ultrafast and Browser Harness. Python 3.12+, Chrome/Chromium, plain HTML/CSS/JavaScript demo, and SQLite.
Highlights
- Real browser QA: visible Chrome by default, optional headless execution, isolated profiles, and explicit policy-approved attachment.
- Bounded Jev decisions: typed operation/target choices over observed controls; exact fixture values and correctness checks remain in code.
- Contract and exploratory runs: check DOM state, correlated HTTP requests/responses, absent requests, and fresh persistence reads; exploration never implies a contract PASS.
- Host-planned exploration: explore lets an authenticated Claude or Codex CLI choose bounded subgoals while Jev remains the browser-action selector.
- Richer observations: accessibility names and form/dialog context, unavailable-control explanations, loaded-text pagination/search, keyboard-driven widgets, and nested scrolling.
- Portable coding-agent skill: Claude Code or Codex can author feature-specific scenarios and run the same CLI. No Todo-specific workflow is required.
Getting started
Prerequisites: Python 3.12+, uv, Chrome/Chromium, and a TypeSafe API key for live runs. Schema, initialization, scenario registration, and validation commands need neither an API key nor a running browser.
Source: community catalog. Details and metrics reflect the published community snapshot and are not a performance endorsement. Documentation details extracted from GitHub · the README.
