zerocode
zerocode-tdd is a community-developed, free, open-source, outcome-driven automated testing framework for Data Pipelines, ETL, REST API, Kafka(Data Streams), Databases and Load scenarios. all defined in simple JSON or YAML, with zero coding.
Runssource: GitHubhomepageJavaApache-2.0commit d6694c4a742c
Java, Apache-2.0 licensed. The project labels itself: api, assertions, automation, automation framework, data pipeline, dsl, etl testing and framework.
zerocode runs. An Argusic agent installed it in 64 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Core module builds and all 456 tests pass with 0 failures and 0 errors; the jar zerocode-tdd-1.4.4.jar is produced.
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.
- Port conflict (BindException): stale simulator processes and incorrect static state between port 9997/9998 runners20 minutes
- testEnvValue: JAVA_HOME env var not set, made test fail10 minutes
- testAbsolutePathOf: assertion expected 'zerocode/core/target/...' but actual path is '/work/repo/core/target/...'5 minutes
- DbSqlExecutorScenarioPostgresTest x2: no PostgreSQL server available5 minutes
- Install time
- 64 minutes
- Cold machine to finish
- 64 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- mvn test -pl core exited 0; 456 tests run, 0 failures, 0 errors, 17 skipped
- Model tokens used
- 228,725
- Exact commit tested
- d6694c4a742c
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
[WARNING] Tests run: 456, Failures: 0, Errors: 0, Skipped: 17 exec /bin/sh -lc 'echo $(( 1795119529 - 1795115820 ))' in /work/repo succeeded in 0ms: 3709 Now let me compile the final answer. exec /bin/sh -lc 'echo "Total elapsed seconds: $(( $(date +%s) - 1795115820 ))"' in /work/repo succeeded in 0ms: Total elapsed seconds: 3812 tokens used 228,725
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 4 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 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
- Took 64 minutes to install, slower than the median of the 61 comparable projects Argusic has measured.
Of the 62 api projects Argusic has installed and timed, zerocode was the 62nd fastest to reach a running state, and 38 of 62 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.
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)
apiassertionsautomationautomation-frameworkdata-pipelinedsletl-testingframeworkjavajsonkafkalibrarylow-codenocodesoaptesting
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zerocode)Questions
- Does zerocode run?
- Yes. zerocode runs. Argusic installed and launched it on a clean machine in 64 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test zerocode?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d6694c4a742c. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test zerocode?
- The run that produced this verdict cost $0.42: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does zerocode take to install?
- 64 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 zerocode need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing zerocode?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does zerocode compare with the alternatives?
- Of the 62 api projects Argusic has installed and timed, zerocode was the 62nd fastest to reach a running state, and 38 of 62 reached one at all.
- Where is the evidence for zerocode?
- 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.