Metadata-Version: 1.1
Name: gabbi
Version: 0.4.0
Summary: Declarative HTTP testing library
Home-page: https://github.com/cdent/gabbi
Author: Chris Dent
Author-email: cdent@peermore.com
License: Apache-2
Description: .. image:: https://travis-ci.org/cdent/gabbi.svg?branch=master
            :target: https://travis-ci.org/cdent/gabbi
        .. image:: https://readthedocs.org/projects/gabbi/badge/?version=latest
            :target: http://gabbi.readthedocs.org/en/latest/
            :alt: Documentation Status
        
        gabbi
        =====
        
        Gabbi is a tool for running HTTP tests where requests and responses
        are represented in a declarative form.
        
        It is under active development. See the YAML files for examples of
        working tests and the docs_ for more details on features and
        formats.
        
        .. _docs: http://gabbi.readthedocs.org/
        
        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,py33
        
        Or 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 | subunit2pyunit
        
        
Platform: UNKNOWN
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: Information Technology
Classifier: Environment :: Web Environment
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Operating System :: POSIX
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
Classifier: Topic :: Internet :: WWW/HTTP :: WSGI
Classifier: Topic :: Software Development :: Testing
