embedded-database-spring-test
A library for creating isolated embedded databases for Spring-powered integration tests.
Runssource: GitHubJavaApache-2.0commit 78158b2dfa12
Java, Apache-2.0 licensed. The project labels itself: embedded database, embedded postgresql, flyway, h2 database, liquibase, mariadb, mssql and mysql.
embedded-database-spring-test runs. An Argusic agent installed it in 25 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Compilation succeeds and the default Gradle test task passes with 0 failures, including real embedded PostgreSQL provider unit tests.
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 93.5 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.
- Docker daemon unavailable; tests defaulting to Docker provider failed5 minutes
- No JDK found in container3 minutes
- Initdb locale 'cs_CZ.UTF-8' not available in container (only C, C.utf8, POSIX)2 minutes
- Install time
- 25 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- ./gradlew test exited BUILD SUCCESSFUL; 66 test classes, 47 test methods, 0 failures, 0 errors
- Model tokens used
- 174,035
- Exact commit tested
- 78158b2dfa12
- 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.
echo "=== End of summary ==="' in /work/repo succeeded in 0ms: === Build elapsed === 1789272960 === End of summary === exec /bin/sh -lc 'echo "Start approximate: 04:16" ; echo "Now: $(date)"' in /work/repo succeeded in 0ms: Start approximate: 04:16 Now: Sun Sep 13 04:41:15 UTC 2026 tokens used 174,035
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 3 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 25 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 embedded-database projects Argusic has installed and timed, embedded-database-spring-test was the 4th fastest to reach a running state, and 4 of 4 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 87.00 | 0.09 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.13 |
Topics (from GitHub)
embedded-databaseembedded-postgresqlflywayh2-databaseliquibasemariadbmssqlmysqlpostgrespostgresqlspring-bootspring-frameworkspring-testtestcontainers
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/embedded-database-spring-test)Questions
- Does embedded-database-spring-test run?
- Yes. embedded-database-spring-test runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test embedded-database-spring-test?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 78158b2dfa12. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test embedded-database-spring-test?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does embedded-database-spring-test take to install?
- 25 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 embedded-database-spring-test need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing embedded-database-spring-test?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does embedded-database-spring-test compare with the alternatives?
- Of the 4 embedded-database projects Argusic has installed and timed, embedded-database-spring-test was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for embedded-database-spring-test?
- 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.