On 25 mars 2013, at 20:20, Stephen Burrows <[email protected]> wrote:
> django-nose is pretty useful for handling test discovery issues, if you're > looking for a quick fix. I don't suffer from this problem because I use a custom test runner to avoid it. My goal here is to improve the framework for others. These days, about 5% of the new valid tickets are a variant of this. Here's one from three days ago: https://code.djangoproject.com/ticket/20114 I've committed a few patches of this kind, and now I regret it. Mechanically adding an override_settings for each case reported to us doesn't improve the code base. On the contrary, it adds noise. I realize that when we started fixing such bugs with override_settings, we embarked on a sisyphean task that degrades the readability of the tests. It seems unrealistic to guarantee that all contrib apps tests will pass with any combination of settings, and this will be a constant source of bugs when we add new tests or new settings. So, from now on, I'll dutifully watch these tickets pile up, and enjoy the little nudge about the deficiency in Django's testing tools, which I don't feel qualified to address. I'm disappointed but let's move on, this isn't a big deal :) -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
