Just to chime in with what others have suggested, Create your dummy user(s) and data on a test version of the application. Bugfix on the test version (if you absolutely have to) and, once you're happy, recreate the database on test from the live server db content and structure. This automatically gives you a test db identical to live and also gets rid of all your junky test data. It really is the easiest / safest way Paul -----Original Message----- From: thelist-bounces at lists.evolt.org [mailto:thelist-bounces at lists.evolt.org] On Behalf Of Matt Warden Sent: Tuesday, November 28, 2006 8:01 AM To: thelist at lists.evolt.org Subject: Re: [thelist] Testing a Webapp On 11/27/06, Hershel Robinson <hershel at galleryrobinson.com> wrote: > there, but at some point, we will also want to test on the live site, > because there is no replacement for the real thing. :) Well, there should be. You should have a testing environment with the production codebase. If you need to test with production data, then mirror the data as well (by snapshot or nightly, depending on how serious your needs are). -- Matt Warden Cleveland, OH, USA http://mattwarden.com This email proudly and graciously contributes to entropy. -- * * Please support the community that supports you. * * http://evolt.org/help_support_evolt/ For unsubscribe and other options, including the Tip Harvester and archives of thelist go to: http://lists.evolt.org Workers of the Web, evolt !