Double imports when migrating from standard Django tests #21

andrejtokarcik opened this Issue Mar 3, 2011 · 0 comments


None yet

1 participant


A usual way to organize Django tests is to split up the file into a tests directory/module whose init file imports other test files in order to make them available for Django. This may cause a little trouble when adopting Django Sane Testing which does an automatic discovery (via nose) and thus may end up with some tests loaded and run twice.

A nose plugin to filter duplicates in the loaded tests list before running the tests, perhaps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment