Available for PostgreSQL

They manage the change. We verify it.

Migration tools deploy your change safely. None of them check the logic still behaves the same.

How to do it

Pin behaviour as tests, then let any change prove itself against them.

Generate tests for the current behaviour and commit them next to your migrations:

unitautogen --schema public --out unit_tests --html report.html --json report.json

After a migration redeploys a function or trigger, re-run the suite in CI.
A moved behaviour fails, naming the routine and branch. If the change was intended, regenerate and commit.

For flows that span several routines, pin them with unitautogen integration (Team).

Top rows show what those tools do well. Bottom rows show the layer none of them offer.

Capability	Redgate Flyway	Liquibase	Bytebase	UnitAutogen
Version-control and apply schema migrations	Yes	Yes	Yes	Works alongside
Approval workflows and change governance	Yes	Yes	Yes	Works alongside
Structural schema drift detection	Yes	Yes	Yes	Works alongside
Deploy functions, triggers and procedures	Yes	Yes	Yes	Tests them
Auto-generate unit tests for that logic	No	No	No	Yes
Auto-generate integration tests across the call map	No	No	No	Yes
Measured branch and statement coverage of PL/pgSQL	No	No	No	Yes
Proof a change preserved behaviour (regression gate)	No	No	No	Yes
Prove RLS and tenant isolation hold through functions, views and triggers	No	No	No	Yes
Audit PII leaked through error and RAISE messages	No	No	No	Yes

Data masking (Redgate, Bytebase) is a separate job from proving access rules hold.

Verifying a change with tests in CI is what the platform tells you to do.

Supabase encourages automated pgTAP tests, run in CI with supabase test db. UnitAutogen generates them, so a change that moves a behaviour fails there. Supabase, Testing your database →
Supabase ships pgTAP as its unit-testing extension. UnitAutogen emits standard pgTAP you commit next to your migrations. Supabase, pgTAP unit testing →
Supabase ships plpgsql_check for PL/pgSQL. UnitAutogen uses it for the branch coverage behind the regression gate. Supabase, plpgsql_check →