Here's two ideas: 1. Set up replication, with your test db the replication slave of your production database, such that changes in production are mirrored in t

Here's two ideas: 1. Set up replication, with your test db the replication slave of your production database, such that changes in production are mirrored in testing nearly instantly. 2. Take your production database backups (you do have those, right?) and restore them to the test database. This is less fresh than a replication setup but if you're just doing functional testing it should be enough to say "Well, okay, this little change isn't going to blow everything up."