Closed meshy closed 9 years ago
I was thinking that Django might have a method to query the non-related fields and related fields separately which might have helped here but I didn't find anything relevant here.
I think that ._meta.get_all_field_names()
is deprecated, so we should perhaps replace it with something in incuna-test-utils
.
That said, I can't help but question the use of the test now.
Perhaps field_names
is appropriate here?
Sounds like a plan.
Alternatively, is there a better way to create the subclasses we're testing?
@Ian-Foote field_names
returned a very similar list of fields, and did include the two that are making the tests fail.
Ah, that's a pity.
I added the new fields to what the test expected.
\o/
There's a failing test related to testing the fields on Route. In django 1.8 we seem to be getting the related names of models that were created in other test methods.