#23879: We should use test-skipping, not conditional discovery in runtests.py
--------------------------------------+------------------------------------
Reporter: carljm | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by wrwrwr):
I can confirm that removing the GIS toggle already gives a bunch of
skipped tests without any failures or errors.
On the other hand, postgres tests can't be dealt with easily --
`postgres_tests` have some migrations that rely on PostgreSQL specific
operations, and cause the test database creation to fail with any other
backend. Resolving this would require some way to limit migrations or
whole test apps to specific backends.
I was able to get it to work with an
[https://github.com/wrwrwr/django/compare/feature/always-test-gis-and-
postgres ad-hoc solution] (that wasn't properly thought over or
researched). It may be an interesting question how to deal with database-
specific migrations in reusable apps.
--
Ticket URL: <https://code.djangoproject.com/ticket/23879#comment:5>
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/064.dfbd47b423c6cc4cc6c4d563a7078768%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
