User repository on GitHub
Evidence-driven frontend QA built on Jev Ultrafast and Browser Harness, with a synthetic todo demo.
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
Python 3.12 CLI that drives real Chrome through Browser Harness and asks Jev to pick each next browser operation and target, while scenario fixtures, deterministic assertions and fresh persistence reads decide the actual contract verdict.
User repository on GitHub
Evidence-driven frontend QA built on Jev Ultrafast and Browser Harness, with a synthetic todo demo.
Repo stats from the GitHub API, cached Oct 2026.
Evidence-driven frontend QA built on Jev Ultrafast and Browser Harness. Python 3.12+, Chrome/Chromium, plain HTML/CSS/JavaScript demo, and SQLite.
Quoted from the project's README. Read the full README.
Watch out
Jev receives redacted structured page observations, not screenshot pixels; screenshots are written locally and are unredacted, so they need explicit policy permission. A TypeSafe key is required for browser runs but not for schema, init or validation commands. The CLI validates and authorizes itself and starts a private browser session unless attaching was authorized; it never starts your app server. init writes jevqa/policy.json with no permitted origins and no model disclosure, so an unchanged policy intentionally blocks a live run, and installing the skill is not that approval. There is no offline-model fallback in the production CLI. Planned exploration additionally requires allow_page_text and allow_planner, the latter defaulting to false, and runs the host CLI with tools disabled. Copy reviewed against the repository README on 2026-10-04, not from running it.
Original write-ups on what this entry is for.
Posts from builders shipping with Jev right now.