testsprite-cli
Official TestSprite CLI, AI-powered automated testing from your terminal
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit 1921dcfe25d9
TypeScript, Apache-2.0 licensed. The project labels itself: ai, cli, e2e testing, playwright, qa, test automation and testing.
testsprite-cli runs, with stand-ins for the services it depends on. An Argusic agent installed it in 9 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install and tsc build succeed; vitest suite passes 4084 tests across 108 files with zero failures; the CLI binary responds with version 0.13.0 and full help text
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- 7 ticker tests failed because NO_COLOR=1 leaked from the container env into ticker.ts's isNoColor() check, making TTY-mode tests enter NO_COLOR mode4 minutes
- Install time
- 9 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test exited 0; 108 test files passed, 4084 tests passed, 2 skipped
- Model tokens used
- 41,807
- Exact commit tested
- 1921dcfe25d9
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**Verification:** - `npm test` exited 0, 108 test files passed, 4084 passed, 2 skipped - `node dist/index.js --version` prints `0.13.0` - `node dist/index.js --help` prints the CLI usage tokens used 41,807 All 108 test files pass with 4084 tests passing. Here's the summary: **Issue found and fixed:** 7 ticker tests failed because the container has `NO_COLOR=1` set as an e… **Verification:** - `npm test` exited 0, 108 test files passed, 4084 passed, 2 skipped - `node dist/index.js --version` prints `0.13.0` - `node dist/index.js --help` prints the CLI usage
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 9 minutes to install, slower than the median of the 77 comparable projects Argusic has measured.
Of the 78 ai projects Argusic has installed and timed, testsprite-cli was the 56th fastest to reach a running state, and 56 of 78 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.04 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.19 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/testsprite-cli)Questions
- Does testsprite-cli run?
- testsprite-cli runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 9 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test testsprite-cli?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1921dcfe25d9. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test testsprite-cli?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does testsprite-cli take to install?
- 9 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does testsprite-cli need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing testsprite-cli?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does testsprite-cli compare with the alternatives?
- Of the 78 ai projects Argusic has installed and timed, testsprite-cli was the 56th fastest to reach a running state, and 56 of 78 reached one at all.
- Where is the evidence for testsprite-cli?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.