> Gunther Birznieks writes: > > the database to perform a test suite, this can get time consuming and > > entails a lot of infrastructural overhead. > > We haven't found this to be the case. All our database operations are > programmed. We install the database software with an RPM, run a > program to build the database, and program all schema upgrades. We've > had 194 schema upgrades in about two years.
But what about the actual data? In order to test my $product->name() method, I need to know what the product name is in the database. That's the hard part: writing the big test data script to run every time you want to run a test (and probably losing whatever data you had in that database at the time). This has been by far the biggest obstacle for me in testing, and from Gunther's post it sounds like I'm not alone. If you have any ideas about how to make this less painful, I'd be eager to hear them. - Perrin
