Hi all, This is a quick call for comment on ticket #12624.
This ticket proposes to make Django's test runner a class-based, rather than function based operation. This makes it much easier to modify the individual parts of the behavior of the Django test runner. For example if you want to: - not destroy the databases at the end of the test run - Use a TestRunner other than the TextTestRunner - Not have DEBUG disabled during tests - Do something else exotic before/during/after test execution you can subclass the basic test runner and override the method that implements the specific behavior that you want to change. Specifically, I want to make this change because I've had a couple of conversations in the recent past that have gone something like: Them: How do you make Django do X before/during/after a test run? Me: You write a custom test runner Them: How do I do that? Me: You copy this 50 line method and modify the 1 line that offends you. Them: 1985 called - they want their code back. I don't expect this change to be especially controversial, but as a matter of good form I thought I raise it before committing. Comments welcome; barring feedback, I'll expect to commit this early next week. 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 django-develop...@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.
