The tests are nested whether they're in the core tests or in contrib. Philosophically this is more a question of coding at a distance. Putting the tests in /tests makes it less obvious which app they actually belong to. Additionally, I'd see the fact that it would be impossible to use manage.py test as a detriment rather than an advantage. If people want to not run the tests for an app, they can always just list the apps they do want to test. Also, django-nose is pretty useful for handling test discovery issues, if you're looking for a quick fix.
--Stephen On Wednesday, March 20, 2013 2:26:33 AM UTC-7, Aymeric Augustin wrote: > > Hello, > > Currently there are three locations for the tests of contrib apps: > - under tests/ — eg. admin > - inside the app — eg. auth > - both — eg. contenttypes > > Following the modeltests / regressiontests merge, I propose to move all > contrib app tests under tests/. This has de following advantages: > - it makes them easier to discover and prevents accidental duplication > - they won't be run by './manage.py test' > - it'll dam up the stream of "if I change setting X then test Y in contrib > app Z fails" > > I'm aware of the idea that contrib apps could include integration tests to > validate that they're properly used within projects, but I don't believe we > have any such tests currently. > > What do you think? > > -- > 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
