I am learning fixtures right now to see if I can use it to successfully solve this problem.
pjjH On Jun 24, 6:11 pm, Chris Withers <ch...@simplistix.co.uk> wrote: > Hi All, > > I'm wondering what the common idiom is for unit testing w.r.t. data and > transactions... > > So, coming from my ZODB background, in unit tests we usually: > > - set up the objects required > - run the code to be tested (which might change, add or delete objects) > - abort the current transaction so no changes are saved and everything > goes back to how it was prior to the start of the test > > What's the equivalent in sqlalchemy-land? > > How do I get test data needed for a specific test to exist for only that > test? > > How do I abort changes made by a test in a unittest.TestCase sublcasses > tearDown method? > > What do I do if the app framework I'm using goes and does a commit as > part of the unit test? (I wish it wouldn't... ;-) ) > > (this is in the context of a Pylons app if that makes things easier/harder) > > cheers, > > Chris > > -- > Simplistix - Content Management, Zope & Python Consulting > -http://www.simplistix.co.uk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
