test-reporter
Displays test results from popular testing frameworks directly in GitHub
Runs with mockssource: GitHubTypeScriptMITcommit 2f9230a92bfa
TypeScript, MIT licensed. The project labels itself: ci cd, github actions, reporting and testing.
test-reporter runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
With Node 24 in PATH, npm ci installed 643 packages, tsc build exited 0, eslint/prettier checks exited 0, npm test passed 177/177, and running the action dist/index.js on the jest-junit fixture exited 0 and produced a summary plus outputs showing 1 passed, 4 failed, 1 skipped.
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.
- System Node.js is v18.19.1 but the repo requires node >=24 (engines and .nvmrc v24); npm ci/typescript/jest failed to work correctly1 minute
- First app launch failed with 'Unable to access summary file: /tmp/ghsum/summary.md' because GITHUB_STEP_SUMMARY file did not exist1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm test exited 0 (21 suites, 177 tests, 30 snapshots passed); node dist/index.js exited 0 and wrote a markdown summary '1 passed, 4 failed, 1 skipped' and emitted outputs conclusion=failure, passed=1, failed=4, skipped=1, time=191
- Model tokens used
- 65,144
- Exact commit tested
- 2f9230a92bfa
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Missing GITHUB_STEP_SUMMARY file on first app launch → fixed by pre-creating file. - test_depth: tier2_mock (verified local-report-summary behavior with real fixture data; GitHub-con… - verified_how: "npm test exited 0 (21 suites, 177 tests, 30 snapshots passed); node dist/index.js … - notes: Node 24 installed locally at ~/node24 (no root); action is a GitHub Action so real deploym… - final_state: one sentence with only observed facts. Let me set the final_state carefully: "Node 24 + npm ci installed, tsc build exited 0, npm test pas… That contains only facts I observed. Good. Let me produce the final line. I have all the verification I need. Let me provide the final report. tokens used 65,144 I have all the verification I need. Let me provide the final report.
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
- Installed in 2 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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.
Of the 8 ci-cd projects Argusic has installed and timed, test-reporter was the 4th fastest to reach a running state, and 6 of 8 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.03 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.01 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/test-reporter)Questions
- Does test-reporter run?
- test-reporter runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test test-reporter?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2f9230a92bfa. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test test-reporter?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does test-reporter take to install?
- 2 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 test-reporter need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing test-reporter?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does test-reporter compare with the alternatives?
- Of the 8 ci-cd projects Argusic has installed and timed, test-reporter was the 4th fastest to reach a running state, and 6 of 8 reached one at all.
- Where is the evidence for test-reporter?
- 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.