> My ideal API for testing would enable me to easily specify a separate > testing DB (maybe via a test.cfg file?) and then the tests would all run > against that with no further setup. Then I could distribute a testdb as > part of the app as a SQLite file.
I've also talked about test.cfg in the past and I still believe it is the best approach... If it doesn't come out, you can write one script that replaces the database for the testing database (using Python, Perl, sed, awk, whatever), runs the tests, replace the database back for the development database (same tool). It works, but requires some extra work that is not easy everywhere (using Python would make it work everywhere TG worked but it requires more than just two lines like the sed version... ;-)). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
