Changes between Initial Version and Version 2 of Ticket #18412


Ignore:
Timestamp:
Jun 1, 2012, 6:35:36 AM (13 years ago)
Author:
Ramiro Morales
Comment:

(s/syncdb/inspectdb/g in ticket summary and description).

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #18412

    • Property Summary Make syncdb regression tests to introspect a manageable database → Make `inspectdb` regression tests introspect a manageable database

  • Ticket #18412 – Description

    initial v2  
    1 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).
     1Currently, 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).
    22
    33This makes creating new test cases for the introspection functionality harder that it should because one needs to peruse a gigantic models.py file.
    44
    5 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?.
     5Maybe 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?.
Back to Top