Opened 18 years ago
Closed 18 years ago
#4153 closed (duplicate)
testing is coupled to models.py
Reported by: | thebanana | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | Testing framework | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The default TESTRUNNER will not run tests in an app that does not have a models.py module. I'm not sure if this is by design (although I'd like to see it try to run the tests anyway). Regardless, the documentation should reflect this since it is the current behaviour.
The use-case for having the TESTRUNNER proceed with tests even without a models.py is when you have Django serving up a site whose models all reside in other libraries (e.g. extensive data model library for legacy system). We tout Django as being flexible enough to run without using the Django ORM - testing should be the same.
Change History (2)
comment:1 by , 18 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 18 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Looks like the same root cause as #3310. Closing as a dupe.