Q: overriding settings

Is there a recommended way to override settings for the live server? Normally I’d use @override_settings(DEBUG=True) so I can see tracebacks while debugging, but had to settle for this:

def before_scenario(context, scenario):
    if "DEBUG" in scenario.tags:
        from django.conf import settings
        settings.DEBUG = True

(and corresponding after_scenario())

It works, but is there a better way?

[graingert]

@farcepest are you still alive?

[pydolan]

It makes sense to me for settings to work similar to how behave-django allows fixture loading, where behave-django would support both of the following options:

Interface:

Option 1: in before_scenario

In this example, we override settings for a particular scenario. Since a new test class is instantiated for each scenario, teardown is automatic:

def before_scenario(context, scenario):
    if scenario.name == 'User login with valid credentials':
        context.override_settings = {'DEBUG': True, 'LOGIN_URL': '/login/here'}

Option 2: via decorator on step functions

In this example, we define a Given Step that uses the behave_django.decorators.override_settings decorator, which behave-django would use to override django’s settings for the entire scenario:

• Step function:

  @override_settings(DEBUG=True, LOGIN_URL='/login/sso')
  @given('I enable debugging and login with SSO')
  def step_impl(context):
      pass
  

• Gherkin file:

  Scenario: User login with valid credentials
      Given I enable debugging and login with SSO
      When I login with "test" and "test"
      Then I see content "Welcome"
  

Implementation:

I’m assuming that in the code where behave-django adds fixtures to the TestCase class, the django settings can also be overwritten. This can possibly be done with django.test.utils.override_settings, either using the class as a context, or mimicking what the decorate_class method is doing. Thoughts?