Community Edition, free

Unit tests and coverage

The default command. A full pgTAP suite for every function and trigger, run for you, measured.

Valid inputs, low and high boundaries
One test per branch, true and false side
Dynamic SQL measured, where static parsers leave it out
Result-set shape and rows matching recorded output
Triggers fire the write and assert what happened

Standard pgTAP. Commit it, run with runtests() or pg_prove.

Function drill-down: per-test results and the annotated source with covered and uncovered lines

A function drill-down showing each generated test and the annotated source of what ran.

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 --schema public

On Windows PowerShell, set it with $env:DATABASE_URL="postgresql://user:pass@host:5432/mydb". The standard PG* variables work too. Connecting →

Unit testing is the default command, so there is no command word. On Supabase, run unitautogen --supabase --schema public from your project. It connects to the local Supabase database itself.

Every uncovered line is explained

Coverage is measured by running the tests. Each uncovered line is tagged with whose problem it is.

Dead code (D)

Can never run. Contradictory conditions named. Usually a real bug.

Error-recovery (H)

Exception handler valid data cannot reach. Untested by default; opt in.

Tool limit (E)

No test could be produced for this line. Reported plainly.

A branch that cannot be tested reliably is NOT_TESTABLE with a reason
Never faked into a green pass

Trigger drill-down: the effect of each firing and the trigger function source

A trigger drill-down showing the effect of each INSERT, UPDATE and DELETE, and the trigger function's source.

Get started Back to overview

What platforms suggest

UnitAutogen uses exactly the tools PostgreSQL and Supabase point you to.

Supabase ships pgTAP as its unit-testing extension and runs it as the test runner. UnitAutogen emits standard pgTAP. Supabase, pgTAP unit testing →
Supabase encourages automated tests for your schema, functions and policies. UnitAutogen generates them. Supabase, Testing your database →
Supabase ships plpgsql_check, the PL/pgSQL linter. UnitAutogen uses it to measure real line and branch coverage. Supabase, plpgsql_check →