Like Carl and Travis said, Django's test runner supports the notion that a Django app has all it's test cases collected in the `models` and `tests` module.
Most of the time, If your app's `tests` module gets too crowded, fracturing the app into smaller apps works. However, if you have to go for the test package approach to maintain sanity, your missing the necessary tools to manage a growing number of test cases; for instance, if you organize your test cases into several modules, there's really no way you can run test cases from a specific module only, without providing a custom test runner or somehow passing arguments to a `suite()` implementation. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/76JePQ022ZEJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
