semvec/pypi-packages huggingface dataset:
django-responsediff 0.8.1
HTTP response diffing against fixtures for testing
License: MIT
Keywords: django test response fixture diff

.. image:: https://travis-ci.org/yourlabs/django-responsediff.svg
    :target: https://travis-ci.org/yourlabs/django-responsediff
.. image:: https://codecov.io/github/yourlabs/django-responsediff/coverage.svg?branch=master
    :target: https://codecov.io/github/yourlabs/django-responsediff?branch=master
.. image:: https://badge.fury.io/py/django-responsediff.png
   :target: http://badge.fury.io/py/django-responsediff

django-responsediff
~~~~~~~~~~~~~~~~~~~

I'm pretty lazy when it comes to writing tests for existing code, however, I'm
even lazier when it comes to repetitive manual testing action.

This package aims at de-duplicating view tests inside the political-memory
itself and to make it reusable for other apps.

It's pretty much the same as django-dbdiff, except this is for HTTP response.

.. note:: v0.7 supports up to Django < 2.1

Response state assertion
========================

When my user tests, he browses the website and checks that everything is
rendered fine. This app allows to do high-level checks of HTML rendering.

See responsediff/response.py docstrings for example usage, or use the
conveniance mixin::

    from responsediff.test import ResponseDiffTestMixin

    class MixinTest(ResponseDiffTestMixin, test.TestCase):
        def test_admin(self):
            self.assertResponseDiffEmpty(test.Client().get('/admin/'))

The above will fail on the first time with ``FixtureCreated`` to indicate that
it has written
``responsediff/tests/response_fixtures/MixinTest.test_admin/{content,status_code}``.
This file is meant to be added to version control. So next time this will run,
it will check that ``response.status_code`` and ``response.content`` is the
same, in future version, or in other configurations (ie. py35, py27, pypy, etc
...).

Instead of deleting the fixtures manually before running the tests to
regenerate them, just run your tests with FIXTURE_REWRITE=1 environment
variable. This will overwrite the fixtures and make the tests look like it
passed.

Requirements
============

Python 2.7 and 3.4 are supported along with Django 1.7 to 1.10 - it's always
better to support django's master so that we can **upgrade easily when it is
released**, which is one of the selling points for having 100% coverage.

Install
=======

Install ``django-responsediff`` with pip.

Related app
===========

A somewhat similar app which inspired django-responsediff is `django-test-utils
<https://github.com/ericholscher/django-test-utils>`_.