3c1a4db019
Because the unittest and pytest runners handle the gabbi test suites and fixtures differently, testing coverage from just the unittest side is incomplete and potentially misleading. The changes here include: * adding a pytest-cov tox target to do coverage from pytest output is in html, put into the default 'htmlcov' directory (the cover target's output goes into the directory 'cover') * adding the pytest-cov module to test-requirements.txt * adjusting both coverage tests so coverage of the tests are not included in the reports, just the "real" code * adding the artifacts from these additions to .gitignore Sadly (but goodly), the result of these changes is that gabbi's coverage sorts are not as bigly as they should be. With the help of these new reports we'll make gabbi's test coverage great again. |
||
|---|---|---|
| docs | ||
| gabbi | ||
| .coveragerc | ||
| .gitignore | ||
| .testr.conf | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-failskip.sh | ||
| test-limit.sh | ||
| test-requirements.txt | ||
| tox.ini | ||
Gabbi
Gabbi is a tool for running HTTP tests where requests and responses are represented in a declarative YAML-based form. The simplest test looks like this:
tests:
- name: A test
GET: /api/resources/idSee the docs for more details on the many features and formats for setting request headers and bodies and evaluating responses.
Gabbi is tested with Python 2.7, 3.4, 3.5 and pypy.
Tests can be run using unittest style test runners, pytest or from the command line with a gabbi-run script.
There is a gabbi-demo repository which provides a tutorial via its commit history. The demo builds a simple API using gabbi to facilitate test driven development.
Purpose
Gabbi works to bridge the gap between human readable YAML files that represent HTTP requests and expected responses and the obscured realm of Python-based, object-oriented unit tests in the style of the unittest module and its derivatives.
Each YAML file represents an ordered list of HTTP requests along with the expected responses. This allows a single file to represent a process in the API being tested. For example:
- Create a resource.
- Retrieve a resource.
- Delete a resource.
- Retrieve a resource again to confirm it is gone.
At the same time it is still possible to ask gabbi to run just one request. If it is in a sequence of tests, those tests prior to it in the YAML file will be run (in order). In any single process any test will only be run once. Concurrency is handled such that one file runs in one process.
These features mean that it is possible to create tests that are useful for both humans (as tools for improving and developing APIs) and automated CI systems.
Testing
To run the built in tests (the YAML files are in the directories
gabbi/gabbits_* and loaded by the file
gabbi/test_*.py), you can use tox:
tox -epep8,py27,py34Or if you have the dependencies installed (or a warmed up virtualenv) you can run the tests by hand and exit on the first failure:
python -m subunit.run discover -f gabbi | subunit2pyunitTesting can be limited to individual modules by specifying them after the tox invocation:
tox -epep8,py27,py34 -- test_driver test_handlersIf you wish to avoid running tests that connect to internet hosts,
set GABBI_SKIP_NETWORK to True.