On Sat, Jul 12, 2014 at 1:06 AM, Tim Graham <[email protected]> wrote:
> With the test discovery changes in 1.6, the tests for django.contrib apps > are no longer run as part of a user's project. For this reason I believe we > no longer need to decorate tests in contrib.auth, formtools, and flatpages > with @skipIfCustomUser. Is that correct? If so, should we keep the > decorator at all? It is documented, but it's not clear to me if the test > runner changes were meant to discourage writing these sort of "integration" > tests or not. > I can see one reason to keep the decorator -- both in Django's test suite, and as a general utility: Projects that are intending to keep their test suites on the "old" discovery mechanism. My own codebase is 4 years old, and has a large test suite; I've dutifully upgraded every Django version (with very little effort, I might add), but re-engineering the entire test suite is probably not something I'm going to do (at least, not until I've got spare time... hahahahahaha :-) So, I'm probably going to package or vendor out the old runner so that my test suite will keep running. @skipIfCustomUser may not have a use in Django's own test suite, but I can see it being useful for a while for projects that are migrating (slowly) away from the old test runner. Russ %-) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq848c5Dpbwenbs%3DpOv5KABERWAp_JdKshUXxfpcyXJWSoVg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
