Opened 12 years ago
Last modified 11 years ago
#18412 closed Cleanup/optimization
Make `inspectdb` regression tests introspect a manageable database — at Version 2
| 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 (last modified by )
Currently, the tests in our test suite direct the inspectdb 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 our tests and direct/restrict the models in regressiontests/inspectdb/models.py to such DB by using a router?.
Change History (2)
comment:1 by , 12 years ago
| Summary: | Make syncdb regression tests to introspect a manageable database → Make syncdb regression tests introspect a manageable database |
|---|
comment:2 by , 12 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | Make syncdb regression tests introspect a manageable database → Make `inspectdb` regression tests introspect a manageable database |
Note:
See TracTickets
for help on using tickets.
(s/syncdb/inspectdb/g in ticket summary and description).