Stephen F. Steiner wrote: > We just have the test harness only access the 'dummy' database. > > The test suite clears out the 'dummy' database, then fills it with known > data (which we store in memory for quick compares). > > Then, we run the data sucking portion of the live code against the > 'dummy' database. > > Compare to the stored data; they'd better match! > > None of that really has anything to do with Pylons specifically since > the data sucking code only provides data for the front end.
Ok, so on a more specific note, how people here manage their test databases? How do you create a dummy/temporary database in fixture, populate data, do tests, then cleanup? How do I do this with PostgreSQL? There seems to be no doco on this whatsoever online... If someone teaches me, I'll make the doco myself for everyone else to use. Carlo > > Testing the front end is another issue altogether. > > If I understand your situation, it should be pretty simple to say "For > this data, we expect this front end output." > > If you make sure your test data includes data that will provoke any > fixed bugs, to make sure they're fixed (and stay fixed!), you should be > all set. > > S > > Stephen F. Steiner > Integrated Development Corporation > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > www.integrateddevcorp.com <http://www.integrateddevcorp.com> > (603)433-1232 > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
