Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'm happy to say that I don't have to work with MySQL. The test suite for our Postgres-based app has several thousand tests grouped into directories. The database is re-initialised for each directory. The initialisation was based on replaying the original SQL/DDL followed by a bunch of schema patches, but that got really slow. We switched to using a dump of the DB and using pg_restore for each test directory and that was much faster. The next step was when someone realised that the Postgres createdb command can take an optional parameter specifying which existing DB should be used as a template. So instead of saving a dump of an initialised DB our test framework stores a whole spare DB (per developer).

    Our full test suite takes about 90 minutes to run and it's probably never going to get faster. Generally a developer is only running tests in one directory so the runtime is measured in seconds rather than hours. Once changes have been checked in, the automated smoke testing box runs the whole suite. If all the tests pass, the smoker builds debian packages from the new source and deploys them to the virtual servers in our staging cluster.