On 25 mars 2013, at 20:20, Stephen Burrows 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.
Thes
esday, 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 / re
среда, 20 марта 2013 г., 21:22:10 UTC+6 пользователь Aymeric Augustin
написал:
>
> On 20 mars 2013, at 11:22, Russell Keith-Magee
> >
> wrote:
>
> > Personally, I'd rather see the opposite -- contrib apps containing their
> own tests, and the tests directory containing just the tests for Dja
On 20 mars 2013, at 11:22, Russell Keith-Magee wrote:
> Personally, I'd rather see the opposite -- contrib apps containing their own
> tests, and the tests directory containing just the tests for Django itself.
> That enforces the fact that the apps really are self contained apps, and can
> be
I run a custom DjangoTestSuiteRunner specifically to filter these out.
+1
--
Loic
On Mar 20, 2013, at 4:26 PM, Aymeric Augustin
wrote:
> - they won't be run by './manage.py test'
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To uns
On Wed, Mar 20, 2013 at 5:26 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> 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
>
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
