volkswagen
:see_no_evil: Volkswagen detects when your tests are being run in a CI server, and makes them pass.
Runssource: GitHubJavaScriptMITcommit ae379b4459ee
JavaScript, MIT licensed. The project labels itself: cheat, ci server, continuous integration, defeat, javascipt, nodejs and volkswagen.
volkswagen runs. An Argusic agent installed it in 0.1 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install completes successfully, npm test executes six fixtures and exits 0 with 36 TAP ok assertions, and the packed package installs and suppresses failing assert and Chai checks in CI mode while leaving those failures active outside CI.
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.
- npm test exited 0 but executed no tests because find excluded every .js fixture and xargs ran bare node.1 minute
- test/chai.js failed under CI mode because the Chai shim only neutralized four assert methods, leaving assert.include() active.1 minute
- test/chai.js used nonexistent Chai API names propertyNotVal, propertyNotVal, deepProperty, notDeepProperty, and deepPropertyNotVal.1 minute
- The timing wrapper failed because /usr/bin/time is not installed (exit 127).
- The first consumer smoke test could not resolve chai because it is a dev dependency and was not installed at the consumer root.
- Install time
- under a minute
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm test exited 0 (6 fixtures, 36 TAP ok assertions); npm ci in a clean copy exited 0 and npm test there also exited 0 with 36 TAP ok assertions; npm pack and consumer install of the tarball plus chai@4 tap@11 tape@4 exited 0; CI=true node -e 'require("volkswagen"); require("assert").strictEqual(1,2)' printed CI_ASSERT_AND_CHAI_SUPPRESSED and exited 0, while the same check without CI exited 1.
- Model tokens used
- 61,977
- Exact commit tested
- ae379b4459ee
- 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 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.
Run `npm audit` for details. NPM_TEST_EXIT=0 1..28 1..8 # tests 8 # pass 8 # ok TAP_OK_COUNT=36 Fixed the vacuous test command and Chai 4 compatibility issues. Verification passed with `npm test`… tokens used 61,977 Fixed the vacuous test command and Chai 4 compatibility issues. Verification passed with `npm test`…
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.
- Installed in 0.1 minutes.
- Recovered from all 5 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 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 0.1 minutes after the clone.
Run history
Topics (from GitHub)
cheatci-servercontinuous-integrationdefeatjavasciptnodejsvolkswagen
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/volkswagen)Questions
- Does volkswagen run?
- Yes. volkswagen runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test volkswagen?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ae379b4459ee. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test volkswagen?
- 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 volkswagen take to install?
- 0.1 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 volkswagen need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing volkswagen?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for volkswagen?
- 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.