Django-webtest

Latest version: v1.9.11

Safety actively analyzes 630026 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 8

1.4.2

------------------

- ``REMOTE_ADDR`` is now ``'127.0.0.1'`` by default. This is how
standard django's test client behave.

Please note that this can slow tests down and cause other side effects
if django-debug-toolbar 0.9.x is installed+configured and
``INTERNAL_IPS`` contain ``'127.0.0.1'`` because debug toolbar will
become turned on during tests. The workaround is to remove
django-debug-toolbar middleware during tests in your test settings::

DEBUG_MIDDLEWARE = 'debug_toolbar.middleware.DebugToolbarMiddleware'
if DEBUG_MIDDLEWARE in MIDDLEWARE_CLASSES:
MIDDLEWARE_CLASSES.remove(DEBUG_MIDDLEWARE)

1.4.1

------------------

- ``self.renew_app()`` method for resetting the 'browser' inside tests.

1.4

----------------

- Better auth implementation;
- support for assertRedirects, assertContains and assertNotContains.

1.3

----------------

- Django 1.3 compatibility: test responses are now having 'templates' attribute;
- Django 1.3 compatibility: the way exceptions are handled is changed;
- auto_follow parameter for app.get method (redirect chains will be
auto-followed with auto_follow=True).

1.2.1

------------------

- REMOTE_USER authorization can be disabled.

1.2

----------------

- ``response.template`` and ``response.context`` goodness (thanks Gregor Müllegger);
- tests (thanks Gregor Müllegger);
- csrf checks are now optional (thanks Gregor Müllegger).

Page 7 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.