#25110: A test in test_runner fails
-----------------------------------+------------------------------------
     Reporter:  double-y           |                    Owner:  JMGordon
         Type:  Bug                |                   Status:  assigned
    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 claudep):

 I think I've at least identified the issue. When `test_discover_runner` is
 run and `gis_tests` is not in current test labels, the discovery process
 inside the test fails with the error:
     RuntimeError: Model class gis_tests.geo3d.models.City3D doesn't
 declare an explicit app_label and either isn't in an application in
 INSTALLED_APPS or else was imported before its application was loaded.

 Then that discovery result is not considered as duplicate, hence the test
 failure.

 I don't know right now what's the best resolution would be, apart from
 recreating an embedded app structure inside test_runner or in a
 `../test_discovery_sample`-like dir, which might be overkill just for that
 test.

--
Ticket URL: <https://code.djangoproject.com/ticket/25110#comment:3>
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/066.f4648cacc14c4fb2800412c81bb92cd4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to