On 9/13/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > > So, I'd appeal for skipping tests that cannot succeed, like in this > case.
This is ticket #4788, and it has been accepted as an idea. We just need an implementation. If you want this for a sprint activity, it's all yours. Regarding the implementation - I'm sure the easiest solution will be to put an 'if not mysql' check around the failing tests. However, my preferred solution would fix this at the output layer, rather than the test layer - i.e., let the tests run and fail, but filter the output against a list of known failures so that the failures are reported in the final output as "X tests passed (with Y known and acceptable failures)" rather than the current flood of stack traces. This approach would mean that we don't forget that the tests are actually failing, but we don't let the failures get in the way of an otherwise operational test suite. Of course, I haven't actually looked into this to see how practical/possible it is, so I might be dreaming the impossible dream :-) 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-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
