#23742: Option to run Django tests in reverse
-----------------------------------+--------------------
Reporter: wrwrwr | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------
The idea is to add a `--reverse` option to be able to more thoroughly
check for test side-effects.
Django test suite currently has some tests that have side-effects causing
rare failures in tests usually run before them (or successes in tests
usually run after them?). Debugging such issues is somewhat cumbersome as
the exact test order depends on the environment.
One example is `assertNumQueries` dependence on cache priming (to be
handled in another ticket) causing `test_group_permission_performance` to
fail (for instance just when the full suite is run with a database on a
ramdisk and memcached enabled). With the
[https://github.com/wrwrwr/django/compare/feature/reverse-test-order
branch] you may try:
{{{#!python
./runtests.py admin_views.tests.GroupAdminTest --reverse
}}}
or
{{{#!python
./runtests.py --pair
admin_views.tests.GroupAdminTest.test_group_permission_performance
--reverse
}}}
to see a failure when run after `fixtures` tests.
--
Ticket URL: <https://code.djangoproject.com/ticket/23742>
Django <https://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 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.b87f1dbcc2efbd607622caff8665398f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
