Community Edition, free

Generated tests, honest coverage.

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

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

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

Every uncovered line is explained

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

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

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

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

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

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 →