AVA CLI
The CLI runs Node.js tests concurrently and shows expected-versus-actual differences for an agent to investigate.
- 20,828 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The runner executes project test code with process permissions, including network calls and file writes.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/avaDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The runner executes project test code with process permissions, including network calls and file writes.
This is third-party code. Review the repository files before installing.
What it does
AVA runs Node.js tests with detailed assertion results. An agent can add a regression test, run it in the terminal and inspect value differences. Test files have separate environments and native asynchronous-test support. AVA is installed in the project and called through its test script. Watch mode reruns after changes, while CI features distribute test files and produce machine-readable reporting.
Who it is for. Node.js package developers assigning agent fixes with small asynchronous tests and readable failures.
Good fit when
- A defect needs a test reproducing the value mismatch.
- The project relies on promises and async functions.
- Editing needs repeated test runs after changes.
- Test files should be split across supported parallel CI jobs.
Not a fit when
- You want a globally installed AVA runner.
- Untrusted tests require AVA itself to provide a security sandbox.
- The project uses an unsupported Node.js release.
Example request
Add one AVA regression test, show its failure and fix the code until the rerun passes.Limitations
Install AVA locally inside the target project; global execution is unsupported. Node.js must satisfy the selected release’s engines requirements, so check them before updating dependencies. Concurrent tests can interfere through shared databases or files; separate their test data. Test-file isolation is not a system-permission boundary: tests execute with process access and can contact networks or modify files.
How to disable. Stop watch mode and remove AVA from the test script when changing runners. Test files remain in the project.
FAQ
How do I install and configure AVA?
Run `npm init ava` in the project directory. It installs AVA and prepares the configuration.
How do I run tests?
Use `npm test` after configuring the test script, or `npx ava`.
How do I watch changes?
Run `npx ava --watch`.
What appears for an object mismatch?
The report highlights actual-versus-expected differences and omits repetitive unchanged parts.
Does it require global test functions?
No. Tests import the function from ava instead of relying on implicit globals.
Discussion
No questions or reviews yet.
Related
CLI toolsVercel CLI for testing coding agents on your framework: runs Claude Code, Codex and others and measures the success rate
A local debugger for TypeScript agents: run step trees, CI trajectory checks and portable evidence bundles, with no account.
Microsoft’s CLI controls real terminal sessions, checks visible text and records test runs for investigating failures.
QA agents, skills and an MCP server: test generation, coverage gaps, flaky tests, security scans and chaos testing
The CLI runs QA Wolf flows locally and in CI, refreshes cached tests and helps investigate traces from failed attempts.
Qlty CLI reports duplicate and complex code before refactoring; automatic formatting runs as a separate action.
README in short
Documentation includes TypeScript, snapshot and integration recipes. Built-in reporting removes unrelated stack-trace lines.