> I use Nadav's BrowserSession code extensively. Without it, I probably > wouldn't have any test code because almost our whole application > requires authentication.
This hasn't made it into the trunk and 1.0 yet, but my last conversation with Kevin indicated that he was definitely up for putting this into TurboGears proper. > Also accepting Bill Woodward's DBTest patches would help simplify your > code a lot. Less cleanup when sqlite commits something by accident. I looked into this in some detail, and when you use the testutil.createRequest() your database requests are automatically wrapped in a transaction, which is commited when the request is completed without error. This screws up the transaction rollback in the test cleanup. I think Bill's answer of dropping the tables after each test is a reasonable solution for this, as long as we don't have hundreds or thousands of tables in our database. (But if that's the case SQLObject isn't going to be an easy fit anyway...) Anyway, I believe Kevin already commited this one last night ;) --Mark --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
