#django

i've been working on an OS app for a while now and am having trouble getting tests to pass b/c i have to use @override_settings to set which model to serve as an api

glassresistor: please continue

i have a function called get_search_model and use it everywhere which returns the model set in settings

Koterpillar: here is the get_search_model code https://github.com/codeforamerica/wealthmap/blo...

now in tests i override this to use an ExampleOpportunity which is a model in the app itself like so https://github.com/codeforamerica/wealthmap/blo...

this is of course the doucmented way to do it but because what im doing is effectively lettings a project swap out the model used by forms and restframework

im getting bad results

how do you define "bad results" and what do they have to do with this setting?

Koterpillar: im getting there sorry

Koterpillar: now when i run my tests with the settings defined the same as the override the tests pass just fine but when i use settings different from the override i get lots of errors

Koterpillar: the settings defines what model a restframework api will use

Koterpillar: i've done a bit of debugging but add these two lines of code to the get_search_model function and running my tests

print(search_model)

import inspect ; print(inspect.stack()[1])

and the results look like this http://pastebin.com/2gKqFLTz

so what im setting is that even though once the tests themselves are running the overrides are taking effect but during the initial setup phase its using the settings defined in the settings file

can I see matcher/forms.py?

so the forms, admin, and serializers all get defined with the projects settings instead of the tests settings

also, raise an exception instead, you'll get a full stack trace

Koterpillar: sure although in this case the form and admin are not part of the main app but rather the project and its the serializers with the wrong settings being the issue

Koterpillar: here they are though https://github.com/codeforamerica/longbeach-res...

Koterpillar: its just used for the admin

oh, I see

can you avoid it on module load?

actually, this means you can't import any of those things before apps are loaded

Koterpillar: not sure the serializers have to load on module load because thats how restframework does it, same with forms/admin(luckily those dont matter for this case)

Koterpillar: so i don't think i can force the serializers to load when the views are called because the serializers are collected and cahed similar to how models are to avoid circular dependencies

can you still raise an exception and paste the traceback from when you run tests?

Koterpillar: i've got the sinking feeling the only solution is to have django allow for an app to change settings before the models load but i don't think thats doable for many reasons

Koterpillar: the pastebin includes all of the tracebacks from the tests

no, raise an exception in get_search_model

Koterpillar: sure i mean i was basically doing that just by printing the stack()[1] in the test output but and ill want to skip the errors because the 3rd call is the interesting one to serializers

no

you get the bottom of each trace

I want the entirety of one trace

ok one sec

(it could be just inspect.stack(), but that's hard to read)

also, raw links from pastebin.com look better

Koterpillar: thanks im working making something that looks nice

Koterpillar: here the full trace http://pastebin.com/raw/vHCVwxcC

hmm, so this is after the settings and apps are loaded

this won't generally work with override_settings

Koterpillar: exactly

because the value is effectively cached, rather than used each time

are tests your only problem?

Koterpillar: the application works great and i like the design but im not sure of a way to make the tests work outside of the sample project

Koterpillar: yep

well, if you were to test this app as a library you'd set the settings right globally

if you are testing this as part of a django project, you don't have a choice

Koterpillar: is there a way of testing an application without a sample_project? there didn't used to be

always was

Koterpillar: really?