puppetry
Web testing solution for non-developers on top of Puppeteer and Jest
Runssource: GitHubhomepageJavaScriptMITcommit d0fdb94cd446
JavaScript, MIT licensed. The project labels itself: browser automation, ci cd, continuous integration, e2e testing, frontend testing, headless testing, no code and puppeteer.
puppetry runs. An Argusic agent installed it in 4 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install succeeds, webpack build succeeds, all 21 unit test suites pass (261 tests), and the Electron app launches on the virtual display logging renderer initialization.
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 100 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.
- [email protected] (pulled by enzyme) depends on undici which references browser globals (ReadableStream, Blob, performance, Event, TextDecoder) not available in Jest 24 node environment2 minutes
- Jest 24 resolver does not support the node: protocol prefix (e.g. require('node:stream')) used by modern dependencies like parse5-parser-stream, encoding-sniffer, htmlparser2, minipass, undici1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm test via 'npx jest --config=jest.cfg.unit.js' exited 0, 21 suites passed, 261 tests passed
- Model tokens used
- 288,791
- Exact commit tested
- d0fdb94cd446
- 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
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 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
succeeded in 52155ms: === Final verification === Unit tests: Test Suites: 21 passed, 21 total Tests: 261 passed, 261 total Snapshots: 0 total Time: 37.918s, estimated 43s All 21 test suites pass with 261 tests passing and 0 failing. Here's my final report: 2026-11-21T04:58:23.864423Z ERROR codex_core::session: failed to record rollout items: thread 01a1f… tokens used 288,791 All 21 test suites pass with 261 tests passing and 0 failing. Here's my 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
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- 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
- Took 4 minutes to install, slower than the median of the 14 comparable projects Argusic has measured.
Of the 15 browser-automation projects Argusic has installed and timed, puppetry was the 10th fastest to reach a running state, and 13 of 15 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 4 minutes after the clone.
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
Topics (from GitHub)
browser-automationci-cdcontinuous-integratione2e-testingfrontend-testingheadless-testingno-codepuppeteerqa-testingtest-automationui-testingvisual-regressionweb-testing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/puppetry)Questions
- Does puppetry run?
- Yes. puppetry runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test puppetry?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d0fdb94cd446. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test puppetry?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does puppetry take to install?
- 4 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 puppetry need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing puppetry?
- 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 puppetry compare with the alternatives?
- Of the 15 browser-automation projects Argusic has installed and timed, puppetry was the 10th fastest to reach a running state, and 13 of 15 reached one at all.
- Where is the evidence for puppetry?
- 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.