updateTestingRollback failure condition when changeset lacks rollback definition

Objective

Determine how Liquibase handles a changeset that has no explicit rollback definition when updateTestingRollback is run against a schema.

The command applies a changeset, executes its rollback, then reapplies it, but Liquibase does not generate rollback logic for every change type. Raw SQL and destructive operations such as DROP COLUMN typically require an explicit rollback block. Whether a missing rollback causes an immediate failure, a skip, or a version-dependent default remains unclear without checking the target Liquibase release and changelog configuration.

Does updateTestingRollback abort when a changeset lacks a rollback definition, ignore that changeset, or continue using a default behavior? Which Liquibase version and configuration parameters control this outcome?