Opened 13 years ago
Last modified 11 years ago
#18412 closed Cleanup/optimization
Make syncdb regression tests to introspect a manageable database — at Initial Version
| Reported by: | Ramiro Morales | Owned by: | nobody |
|---|---|---|---|
| Component: | Testing framework | Version: | dev |
| Severity: | Normal | Keywords: | inspectdb |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Currently, the tests in our test suite direct the syncdb management command calls to examine the 'default' database that will contain the tables corresponding to all the models of the suite being run (they can be hundreds in the case of the full suite).
This makes creating new test cases for the introspection functionality harder that it should because one needs to peruse a gigantic models.py file.
Maybe we can add a third DB to the DATABASES setting used for out tests and direct/restrict the 'regressiontests.inspectdb' models to such DB by using a router?.
Note:
See TracTickets
for help on using tickets.