A routine run together with what it calls and what it fires, for real.
Full test set per root, with valid inputs, boundaries and one per branch
Run through the actual call chain
Coverage measured across root, callees and triggers
Standalone routines noted, not duplicated
Run it
The database URL goes in the DATABASE_URL environment variable. There is no command-line flag for it.
export DATABASE_URL=postgresql://user:pass@host:5432/mydb
unitautogen integration --schema public
On Windows PowerShell, set it with $env:DATABASE_URL="postgresql://user:pass@host:5432/mydb". The standard PG* variables work too. Connecting →
It picks up your Team licence file automatically. On Supabase, run unitautogen --supabase integration --schema public from your project. It connects to the local Supabase database itself.
The Integration Testing Report
Same four summary cards, measured across the whole call map
One row per root function
Click a root for its call map, in real call order
Per-test write footprint across every table the map touches
Stitched annotated source of every function in the map
A root's call map drill-down.
What an uncovered line means here
The root's inputs never reached it through the whole flow
Not "the callee had no test", since the callee's own unit test still covers it
Part of the Team edition
Same seed data and report format as the unit tests
We would like to log your visit to see how the site is used. That records the page, the site you came from, your IP address and browser, and a random id for this tab. We delete it once we no longer need it.
