Currently overriding the Django urlconf requires a marker, which also requires defining the urlconf at the root of the test module. If you have many tests that need this (with differing patterns and views) this can get quite annoying.
This doesn't seem to be necessary, as the Django urlconf setting can be an object and it can be changed at runtime.
This PR adds a django_set_urlconf fixture that allows you to define the urlconf within the test and set it directly with the fixture:
Currently overriding the Django urlconf requires a marker, which also requires defining the urlconf at the root of the test module. If you have many tests that need this (with differing patterns and views) this can get quite annoying.
This doesn't seem to be necessary, as the Django urlconf setting can be an object and it can be changed at runtime.
This PR adds a
django_set_urlconf
fixture that allows you to define the urlconf within the test and set it directly with the fixture: