Run unitautogen --help to list the five commands and unitautogen <command> --help for one command's full option list. Each command has its own page.
| Command | Purpose | Edition | Generates tests | Main report and folder |
|---|---|---|---|---|
unitautogen | Unit tests and coverage for functions and triggers | Community | Yes | HTML and JSON. Tests in <out>/unit/<schema>/, CI bundle in <out>/unit/ |
unitautogen integration | Tests across the real call map | Team | Yes | HTML and JSON. Tests in <out>/integration/<schema>/ |
unitautogen seccover | Full security-coverage review | Enterprise | Yes | Data security coverage, RLS policy and column-level reports and tests in <out>/security/<schema>/ |
unitautogen pii | PII in error and RAISE messages | Enterprise | Yes | The seccover output, plus <out>/pii_tests/ |
unitautogen hipaa | HIPAA evidence, seccover plus the audit-log check | Enterprise | Through seccover and the trigger tests | <out>/hipaa/<schema>/hipaa_report.html and JSON, stamped |
--schema a,b the schemas to cover--like pat a name filter--out DIR where tests and reports go--html PATH the HTML report--json PATH a machine-readable summary--no-report skip the CI report bundle--no-coverage generate and run only, faster--include-extension also test extension-owned routines--supabase run inside a Supabase project, see Supabase mode--config FILE the config file, ./unitautogen.toml by default--debug [LOGFILE] write a log file to send to support--license PATH the licence file, if it is not found automaticallyPaid commands find the licence file on their own, from unitautogen.lic in the folder you run from, or use --license PATH. See Prerequisites.