Good day, I'm running into some confusion on the intended way to architect tests/ users/etc. I've been playing with the latest SVN snapshot.
I've currently got my test cases setup around: 1) Setup Custom Users, Groups,Permissions that are used for all test cases 2) Change out my authentication middleware (I use CAS for production but local accounts work just fine for unittesting) 3) Add testcases that aren't related to INSTALLED_APPLICATIONS 4) unittest.TestCase()s I've been adding most data manually for testing but would like to move towards using fixtures. Seems like a good job for django.test.TestCase Issues I've encountered: 1) initial_data has bitten me not realizing it was synced in production each time. I think that initial_data should only get inserted if you have an empty new database. Perhaps things synced each time should be called "constant_data". The fixtures documentation in testing does say it gets synched each time but also says its purpose is to populate the initial empty new database. 2) Setting up users/groups/users manually in the runner gets blown away by the TestCase architecture. Works as documented. However, I'm not sure where I should put things that should happen post-each syncdb for testing only. Should there be a testrunner function that gets called post each sync or should I create a single TestCase derived from django.test.TestCase that does the "pre-setup"? 3) DateTime serialization won't work if the date is before 1901 - I have a bug/real life data set where I get some bogus dates out of another system. This is really a python problem. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
