# Run a ChangeLog in "TEST" mode

**URL:** <https://forum.liquibase.org/t/run-a-changelog-in-test-mode/2321>\
**Category:** General Discussion\
**Created:** [July 18, 2013, 7:56pm UTC](https://forum.liquibase.org/t/run-a-changelog-in-test-mode/2321 "2013-07-18T19:56:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![un1374151795591r21id](https://avatars.discourse-cdn.com/v4/letter/u/85e7bf/32.png) [@un1374151795591r21id](https://forum.liquibase.org/u/un1374151795591r21id)\
**Post date:** [July 18, 2013, 7:56pm UTC](https://forum.liquibase.org/t/run-a-changelog-in-test-mode/2321/1 "2013-07-18T19:56:00Z")

</div>

Is there any way to run a complete ChangeLog in test mode. I mean, run it inside a global transaction with a rollback at the end. This will allow the DBA’s to test the whole ChangeLog before applying it to a Production environment.

Thanks

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [July 18, 2013, 7:56pm UTC](https://forum.liquibase.org/t/run-a-changelog-in-test-mode/2321/2 "2013-07-18T19:56:00Z")

</div>

The problem is that most databases will autocommit on DDL statements regardless of what liqubase tries to do.

My suggestion is normally to do a liquibase update against a snapshot of production before actually running it on production.

Nathan