DjangoRestFramework API checker
Project description
================================
DRF API Checker
================================
.. image:: https://badge.fury.io/py/drf-api-checker.png
:target: http://badge.fury.io/py/drf-api-checker
.. image:: https://travis-ci.org/saxix/drf-api-checker.png?branch=master
:target: https://travis-ci.org/saxix/drf-api-checker
.. image:: https://pypip.in/d/drf-api-checker/badge.png
:target: https://pypi-hypernode.com/pypi/drf-api-checker
This module offers some utilities to avoid unwanted changes in Django Rest Framework responses,
so to keep stable contracts
The purpose is to guarantee that any code changes never introduce 'contract violations'
changing the Serialization behaviour.
Contract violations can happen when:
- fields are removed from Serializer
- field representation changes (ie. date/number format, )
- Response status code changes (optional)
- Response headers change (optional)
How it works:
-------------
The First time the test is ran, the response and model instances are serialized and
saved on the disk; any further execution is checked against this first response.
Test data are saved in the same directory where the test module lives,
under `_api_checker/<module_fqn>/<test_class>`
Fields that cannot be checked by value (ie timestamps/last modified) can be tested writing
custom `assert_<field_name>` methods.
In case of nested objects, method names must follow the field "path".
(ie. `assert_permission_modified` vs `assert_modified`)
This module can also intercept when a field is added,
in this case it is mandatory recreate stored test data; simply delete them from the disk
or set `API_CHECKER_RESET` environment variable and run the test again,
in case something goes wrong the output will be
**Field values mismatch**
::
AssertionError: View `<class 'path.to.module.CustomerListAPIView'>` breaks the contract.
Field `name` does not match.
- expected: `Partner 0`
- received: `Partner 11`
**Field remove**
::
AssertionError: View `<class 'path.to.module.CustomerListAPIView'>` breaks the contract.
Field `id` is missing in the new response
**Field added**
::
AssertionError: View `<class 'path.to.module.CustomerListAPIView'>` returned more field than expected.
Action needed api_customers.response.json need rebuild.
New fields are:
`['country']`
How To use it:
--------------
unittest
~~~~~~~~
Using ApiCheckerMixin::
class TestAPIAgreements(ApiCheckerMixin, TestCase):
def get_fixtures(self):
return {'customer': CustomerFactory()}
def test_customer_detail(self):
url = reverse("customer-detail", args=[self.get_fixture('customer').pk])
self.assertAPI(url)
Using ApiCheckerBase metaclass::
class TestAPIIntervention(TestCase, metaclass=ApiCheckerBase):
URLS = [
reverse("intervention-list"),
reverse("intervention-detail", args=[101]),
]
def get_fixtures(cls):
return {'intervention': InterventionFactory(id=101),
'result': ResultFactory(),
}
ApiCheckerBase can produce API test with minimum effort but it is offers less flexibility
than the use of ApiCheckerMixin.
pytest
~~~~~~
pytest integraation is provided by two helpers `frozenfixture` and `contract`::
from django.urls import reverse
from drf_api_checker.pytest import contract
@contract()
def test_url(frozen_detail):
url = reverse("master-list")
return url
Links
-----
+--------------------+----------------+--------------+----------------------------+
| Stable | |master-build| | |master-cov| | |
+--------------------+----------------+--------------+----------------------------+
| Development | |dev-build| | |dev-cov| | |
+--------------------+----------------+--------------+----------------------------+
| Project home page: | https://github.com/saxix/drf-api-checker |
+--------------------+------------------------------------------------------------+
| Issue tracker: | https://github.com/saxix/drf-api-checker/issues?sort |
+--------------------+------------------------------------------------------------+
| Download: | http://pypi.python.org/pypi/drf-api-checker/ |
+--------------------+------------------------------------------------------------+
| Documentation: | https://drf-api-checker.readthedocs.org/en/latest/ |
+--------------------+------------------------------------------------------------+
.. |master-build| image:: https://secure.travis-ci.org/saxix/drf-api-checker.png?branch=master
:target: http://travis-ci.org/saxix/drf-api-checker/
.. |master-cov| image:: https://codecov.io/gh/saxix/drf-api-checker/branch/master/graph/badge.svg
:target: https://codecov.io/gh/saxix/drf-api-checker
.. |dev-build| image:: https://secure.travis-ci.org/saxix/drf-api-checker.png?branch=develop
:target: http://travis-ci.org/saxix/drf-api-checker/
.. |dev-cov| image:: https://codecov.io/gh/saxix/drf-api-checker/branch/develop/graph/badge.svg
:target: https://codecov.io/gh/saxix/drf-api-checker
DRF API Checker
================================
.. image:: https://badge.fury.io/py/drf-api-checker.png
:target: http://badge.fury.io/py/drf-api-checker
.. image:: https://travis-ci.org/saxix/drf-api-checker.png?branch=master
:target: https://travis-ci.org/saxix/drf-api-checker
.. image:: https://pypip.in/d/drf-api-checker/badge.png
:target: https://pypi-hypernode.com/pypi/drf-api-checker
This module offers some utilities to avoid unwanted changes in Django Rest Framework responses,
so to keep stable contracts
The purpose is to guarantee that any code changes never introduce 'contract violations'
changing the Serialization behaviour.
Contract violations can happen when:
- fields are removed from Serializer
- field representation changes (ie. date/number format, )
- Response status code changes (optional)
- Response headers change (optional)
How it works:
-------------
The First time the test is ran, the response and model instances are serialized and
saved on the disk; any further execution is checked against this first response.
Test data are saved in the same directory where the test module lives,
under `_api_checker/<module_fqn>/<test_class>`
Fields that cannot be checked by value (ie timestamps/last modified) can be tested writing
custom `assert_<field_name>` methods.
In case of nested objects, method names must follow the field "path".
(ie. `assert_permission_modified` vs `assert_modified`)
This module can also intercept when a field is added,
in this case it is mandatory recreate stored test data; simply delete them from the disk
or set `API_CHECKER_RESET` environment variable and run the test again,
in case something goes wrong the output will be
**Field values mismatch**
::
AssertionError: View `<class 'path.to.module.CustomerListAPIView'>` breaks the contract.
Field `name` does not match.
- expected: `Partner 0`
- received: `Partner 11`
**Field remove**
::
AssertionError: View `<class 'path.to.module.CustomerListAPIView'>` breaks the contract.
Field `id` is missing in the new response
**Field added**
::
AssertionError: View `<class 'path.to.module.CustomerListAPIView'>` returned more field than expected.
Action needed api_customers.response.json need rebuild.
New fields are:
`['country']`
How To use it:
--------------
unittest
~~~~~~~~
Using ApiCheckerMixin::
class TestAPIAgreements(ApiCheckerMixin, TestCase):
def get_fixtures(self):
return {'customer': CustomerFactory()}
def test_customer_detail(self):
url = reverse("customer-detail", args=[self.get_fixture('customer').pk])
self.assertAPI(url)
Using ApiCheckerBase metaclass::
class TestAPIIntervention(TestCase, metaclass=ApiCheckerBase):
URLS = [
reverse("intervention-list"),
reverse("intervention-detail", args=[101]),
]
def get_fixtures(cls):
return {'intervention': InterventionFactory(id=101),
'result': ResultFactory(),
}
ApiCheckerBase can produce API test with minimum effort but it is offers less flexibility
than the use of ApiCheckerMixin.
pytest
~~~~~~
pytest integraation is provided by two helpers `frozenfixture` and `contract`::
from django.urls import reverse
from drf_api_checker.pytest import contract
@contract()
def test_url(frozen_detail):
url = reverse("master-list")
return url
Links
-----
+--------------------+----------------+--------------+----------------------------+
| Stable | |master-build| | |master-cov| | |
+--------------------+----------------+--------------+----------------------------+
| Development | |dev-build| | |dev-cov| | |
+--------------------+----------------+--------------+----------------------------+
| Project home page: | https://github.com/saxix/drf-api-checker |
+--------------------+------------------------------------------------------------+
| Issue tracker: | https://github.com/saxix/drf-api-checker/issues?sort |
+--------------------+------------------------------------------------------------+
| Download: | http://pypi.python.org/pypi/drf-api-checker/ |
+--------------------+------------------------------------------------------------+
| Documentation: | https://drf-api-checker.readthedocs.org/en/latest/ |
+--------------------+------------------------------------------------------------+
.. |master-build| image:: https://secure.travis-ci.org/saxix/drf-api-checker.png?branch=master
:target: http://travis-ci.org/saxix/drf-api-checker/
.. |master-cov| image:: https://codecov.io/gh/saxix/drf-api-checker/branch/master/graph/badge.svg
:target: https://codecov.io/gh/saxix/drf-api-checker
.. |dev-build| image:: https://secure.travis-ci.org/saxix/drf-api-checker.png?branch=develop
:target: http://travis-ci.org/saxix/drf-api-checker/
.. |dev-cov| image:: https://codecov.io/gh/saxix/drf-api-checker/branch/develop/graph/badge.svg
:target: https://codecov.io/gh/saxix/drf-api-checker
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
drf-api-checker-0.2.0.tar.gz
(20.4 kB
view details)
File details
Details for the file drf-api-checker-0.2.0.tar.gz
.
File metadata
- Download URL: drf-api-checker-0.2.0.tar.gz
- Upload date:
- Size: 20.4 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | c44ce1b01bc6d6fae110715ee5633b9e113563c92f52c866ee011609b4e3b763 |
|
MD5 | 8bfdf9ea38f4069d5166481d08c56032 |
|
BLAKE2b-256 | 82dd99f4900622b51b979c6d1fe15dfd4ffae3d1d6263f497dd31c702f568c1f |