> If you want to pursue this idea of making it easier to define suites, > please open a second ticket - the two ideas don't need to get mixed > together.
I'd prefer to do the original ticket, rather than introduce my own solutions. I don't yet feel strong enough to do that. First, I want to understand more of django internals :-) > Your proposal covers this issue of invoking test suites. This should > be a fairly simple issue to resolve - it's just a matter of modifying > the test runner to look for a suite with the appropriate name before > it goes the process of discovering TestCase instances and building a > default suite. Well, if that's the case and the problem is easier, that I thought, then it's even better :-) Still, I've got a question: if someone creates a suit through a function, how should it be invoked? Only explicitly app.module.suite_function or if run ./manage.py test should this suite be also invoked (and then some tests will be run twice)? -- Filip Gruszczyński --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
