Run it in a transaction, and if it fails, abort the transaction. nbd, did this for years in prod. Discovered some interesting assumptions about sequential IDs in the DB tests while running it against prod under peak load, too!

I don’t consider that “a regular test” but something db-specific that would have a custom workflow.