#12289: Test runner behave improperly when application names are not unique ----------------------------------------------+----------------------------- Reporter: Piotr Czachur <[email protected]> | Owner: nobody Status: new | Milestone: Component: Testing framework | Version: SVN Keywords: | Stage: Unreviewed Has_patch: 0 | ----------------------------------------------+----------------------------- During the time I migrated to Django - which was 2 months ago - I experienced many silent side effect when this "unique app name" constraint was violated: for example, when running test for given application: {{{ python manage.py test auth }}} Django will run tests only for 1st found application with "auth" name, others are just quietly skipped. It's just wrong, I'd like to see exception or tests should be run for all applications with "auth" name.
-- Ticket URL: <http://code.djangoproject.com/ticket/12289> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" 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-updates?hl=en.
