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 pylons-land when using sqlalchemy as a back end?
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?
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
"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
-~----------~----~----~----~------~----~------~--~---
