Testing with legacy data

I'm not a fan of testing with actual data, except maybe as a final run to make sure no existing data breaks something or for stress testing with large amounts of data. Your legacy DB will not cover all of the possible cases that need to be tested in your code. Instead, write quality unit

Re: Testing with legacy data

On Tue, Aug 6, 2013 at 5:59 AM, Jani Tiainen wrote: > Hi, > > I've legacy database that is rather large (around 300MB) containing lot more > than just data (triggers, stored procedures and such). > > Now how I can test with such a data? Preferably I would like to load data to

Testing with legacy data

Hi, I've legacy database that is rather large (around 300MB) containing lot more than just data (triggers, stored procedures and such). Now how I can test with such a data? Preferably I would like to load data to database, run test, rollback changes and run a next test. But I really wouldn't