User repository on GitHub
Local-first test selector using Jev judgments to determine which tests are affected by a code change
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
Jev directory
CommunityJev Tools & CLIs
Leanest
Local-first test selector that asks a judge — classifier.dev by default, or Jev with a TypeSafe key — whether each test could be affected by the current code change, then hands only the selected files to Playwright or Vitest. Uncertainty always runs the full suite.
- Stars
- 5
- Language
- TypeScript
- License
- MIT
- Reading time
- 3 min
- Published by
- Community
- Author
- baronunread
- Last verified
- Oct 2026
- Languages
- TypeScript
- Platforms
- CLIPlaywright
- Capabilities
- Open sourceRuns locally
Highlights
- For each test it asks one judge question — could the change affect behaviour this test verifies? — and skips those confidently ruled irrelevant.
- Fail-open by design: a missing key, timeout or malformed response runs the full suite with a warning; finding no tests at all is exit 1, not a silent pass.
- Deterministic overrides always run: a test whose own file changed, one that statically imports a changed file, or one navigating a changed route's path.
- Whole-suite rules come first: runner setup or lockfile changes run everything and Markdown-only changes skip everything, without asking the judge.
- Defaults to classifier.dev, a free no-auth judge; TYPESAFE_API_KEY plus LEANEST_PROVIDER=jev switches to Jev, and Laya is also supported.
Quickstart
bash
npm install -D leanest
npx leanest playwrightWatch out
Copy reviewed against the repo README on 2026-10-15. The project's framing — determining which tests are safe not to run rather than predicting failures — is its own, and the captured README publishes no accuracy or saved-time figures. Judge quality governs skips, with fail-open as the designed mitigation when the judge is unavailable.
Questions about this entry
Short answers drawn from the linked project or page.
It sits in front of your test runner and selects which tests matter for a given code change. It does not predict which tests will fail; it determines which tests are safe enough not to run, skips the rest out loud, and hands the selected file paths to Playwright or Vitest.
One semantic judgment per test: it packages the diff plus the test's source and asks whether the change could affect behaviour the test verifies. Jev is optional — the default judge is classifier.dev, a free no-auth service; setting TYPESAFE_API_KEY and LEANEST_PROVIDER=jev routes judgments through Jev instead.
npm install -D leanest, or bun add -D leanest; it works with npm, pnpm, yarn or Bun. Then npx leanest playwright runs the affected end-to-end tests, npx leanest select playwright only shows the selection, and npx leanest inspect ranks every test by relevance for debugging.
Fail open: a missing API key, an API timeout or a malformed response falls back to running the full suite, loudly, with a warning. The README notes uncertainty means run. If no tests are found at all, that is an exit 1 error rather than a silent pass.
Deterministic overrides: a test whose own file changed, one that statically imports a changed file, or one navigating a route that a changed file's path names — the README's example is page.goto('/admin/users') against a changed routes/admin/users.tsx. Runner setup changes run every test, and Markdown-only changes skip all of them.
No. Leanest selects file paths and hands them to your actual runner, such as playwright test <paths> or vitest run <paths>, leaving reporters, retries, sharding and CI-required-check behaviour alone. Anything after -- passes straight through to the runner.
classifier.dev is the default and needs no key or auth. Jev is supported via TYPESAFE_API_KEY with LEANEST_PROVIDER=jev, and Laya is listed as another option; switching providers changes only the judge, not the selection policy or the runner integration.
More Jev resources like this
Browser QA where Playwright drives and films, and Jev judges: natural-language assertions, self-healing locators and goal-driven click loops, with a JSON-flow CLI for agents, a local dashboard and an agent skill.
Jev Tools & CLIs#community#catalog-import#logicrw
Community
jonymusky/jev-browser-qaTypeScript
jonymusky/jev-browser-qaTypeScriptWrite end-to-end tests for web apps in plain English; jev-e2e turns each case into a plan, has Jev pick the page controls, and runs it with Playwright, returning PASS, FAIL or BLOCKED with HTML, JSON and masked screenshot evidence.
Jev Tools & CLIs#community#catalog-import#madewithjev
Community
perixtar/jev-e2eTypeScript
perixtar/jev-e2eTypeScriptLatitude is an open-source observability platform for AI agents: one line of telemetry captures traces, failing traces group into tracked signals, and fixes are dispatched to coding agents and replayed against real traces.
Jev Tools & CLIs#community#catalog-import#logicrw
Community
latitude-dev/latitude-llmTypeScript
latitude-dev/latitude-llmTypeScriptA local guard layer for AI coding agents: it evaluates delivered tool hooks against deterministic rules, blocks dangerous ones in milliseconds with no model in the decision path, and keeps a grep-able local activity log for auditing.
Jev Tools & CLIs#community#catalog-import#logicrw
An enterprise admin-console test tool that generates replayable Excel test cases from live browser pages, or replays existing Excel cases, driving Playwright with local Laya or a compatible decision API to match fields, options, and targets.
Jev Tools & CLIs#community#catalog-import#madewithjev
Community
anthonyli/laya-pilotJavaScript
anthonyli/laya-pilotJavaScriptA testing app and CLI for chat endpoints: send messages to any chat API, watch replies stream in as a conversation, and check every reply with rule checks (JSONPath, latency, tokens, cost, tool calls) and judged checks including TypeSafe's System One. Export the suites as files and run them in CI.
Jev Tools & CLIs#community#catalog-import#yibie
Community
abhimanyupandian/hafenJavaScript
abhimanyupandian/hafenJavaScriptFrom the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.