Skip to main content

Library for testing api endpoints

Project description

contract-test-framework contains an implementation of contract testing in Python. Under the package name fellowship

How to use from console:

If you want to validate an REST API, run Fellowship in validate mode. If your contracts follow the Jinja2 syntax, make sure that you give the path to config.yaml in environment variable contract_test_config. You can see examples of contracts and config at example_contract.json. Request part of the contract specifies the endpoint to make the request to. While everything under properties defines the JSON schema to validate against. Fellowship validates these contracts against a meta-schema before it makes the request. Example of how to run from console:

$ fellowship validate path/to/contract_directory/

To generate a contract in console, run in generate mode, with the following syntax:: fellowship generate path_of_the contract_to_generate request_kwargs expected_json. Request_kwargs is the request as a dictionary, the dictionary can take following parameters:

  • url: can be given as a full url, or just the endpoint (/api/v1/test)
    it will then fill out the Jinja 2 syntax for you
    {{ config.protocol }}://{{ config.host}}/api/v1/test, when validating
    protocol and config will be filled from config.yaml
  • headers: can be given as a dictionary {“Accept”: “application/json”}, if
    left empty it will automatically fill as
    {{ config.default_headers | jsonify }}.
  • data: The body of the request

The last expected argument is the expected json response from the Rest API. The contract will generate with only types and required for all fields. If you want to validate the values, you need to fill the consts and enums manually.

$ fellowship generate sample.json '{"url": "/test", "method": "GET"}' \
  '{"json": "expected_response"}'

Features

REST endpoint contract testing and contract rendering.

Future development plans includes to support gRPC and message-based communication

Installation

fellowship will be made available on PyPI. You can install using pip:

$ pip install fellowship

Running the Test Suite

If you have tox installed (perhaps via pip install tox or your package manager), running tox in the directory of your source checkout will run fellowship’s test suite.

Contributing

See how to contribute in CONTRIBUTING.rst.

The code and the issues are hosted on GitHub.

The project is licensed under BSD-3-Clause.

The documentation is hosted on read_the_docs

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

fellowship-0.0.4.tar.gz (16.4 kB view details)

Uploaded Source

File details

Details for the file fellowship-0.0.4.tar.gz.

File metadata

  • Download URL: fellowship-0.0.4.tar.gz
  • Upload date:
  • Size: 16.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7

File hashes

Hashes for fellowship-0.0.4.tar.gz
Algorithm Hash digest
SHA256 967cef8caeaa427cd76c954b582cb2bb3913cce31049a9e5db11deae10aaf66a
MD5 9484340ebaa6d226de1c33ba861d09fb
BLAKE2b-256 da42de3fc08a710cb5f98174ddb7cc8f1c1c0c9a4cf3349e6c906747bdb2912c

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page