sqitch-verify - Verify deployed database changes


sqitch verify [options] [<database>]
sqitch verify [options] --from-change <change>
sqitch verify [options] --to-change <change>
sqitch verify [options] --from-change <change> --to-change <change>


Verify that a database is valid relative to the plan and the verification scripts for each deployed change.

More specifically, verify iterates over all deployed and planned changes (or the subset identified by --from-change and/or --to-change) and checks that each:

The <database> parameter specifies the database to which to connect, and may also be specified as the --target option. It can be target name, a URI, an engine name, or plan file path.

Verify tests are scripts that may be associated with each change. If a change has no verify script, a warning is emitted, but it is not considered a failure. If a change has been reworked, only the most recent reworking will have its verify script executed.

Verify scripts should make no assumptions about the contents of the database, as unit tests might. Rather, their job is to ensure that the state of a database is correct after a deploy script has completed. Verify scripts are run through the database engine command-line client, just like deploy and revert scripts. They should cause the client to exit with a non-zero exit code if they fail.


Configuration Variables


Part of the sqitch suite.