There are a couple of problem I am looking at where it will be nice to put in some regression tests just to ensure they don't reoccur. However, putting them in tests/modeltests/* doesn't seem like the right place, because we are simultaneously using that directory as a source for examples. This traditionally doesn't work (mixing "good practice" and "evil, corner-case regression tests").
What I would like to propose is that we create a tests/regression/ subdirectory for these slightly more mind-numbing but important tests. Same sub-directory structure, etc, as the the modeltests/ directory, but not in any way intended to be examples of good model technique. Thoughts? Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
