Hi all, Time for the long promised phase 3 of the Django testing framework - fixtures - to make an appearance. I've attached the changes as a single patch to ticket #2333 (http://code.djangoproject.com/tickets/2333 )
The idea here is to exploit the serialization framework to provide a mechanism for describing the contents of a database during a test. Manage.py has a few new options to allow for the insertion and deletion of test data, as well as a mechanism for dumping the current state of a database as a fixture. For the most part, this is fairly straightforward stuff. Inserting data is easy; however, deleting data is much harder. The simple solution (delete database and recreate) is painfully slow; faster mechanisms are not database independent. I now have an implementation that works pretty well for SQLite, MySQL, and post v8.1 versions of Postgres. It is now at the point where it needs some feedback from others, as well as some input from people with more experience than I on Oracle, MSSQL, and early versions of Postgres. Documentation is also required; I will work on this once the design has been accepted. A full walkthrough of the patch is attached to the ticket; Comments and feedback welcome. Yours Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
