kevlar
Kevlar is an API regression testing framework. It uses a black-box testing methodology to ensure you maintain perfect backwards compatibility as your API evolves.
Tagline
> Keep your API bulletproof.
Installation
It’s in Python, so pip is the way to go:
pip install kevlar
Usage
There are two phases when using kevlar: 1) establishing a baseline and 2) regression testing and accepting/rejecting behavior changes.
First, you define a set of API requests to be made against an API. After kevlar runs your test suite, you’ll carefully review and generalize the responses it recieved back to make sure they’re exactly what you’re expecting.
After you’ve established a baseline, run the test suite on every commit, push, build, or even on an hourly cron job that’ll test production to make sure absolutely nothing has changed in what you’re responding to your clients with. Since APIs evolve and grow overtime, adapt your baseline as appropriate whenever you add new functionality or have differences reported from kevlar.
### Why?
Because manual smoke testing an API is really painful. It’s meant to be consumed by a machine, so let a machine do your smoke testing for you! ʕノ•ᴥ•ʔノ*:・゚✧
### Is it any good?
- thumbsup:
Metadata
Release files for kevlar 0.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| kevlar-0.0.8.tar.gz | 6.4 kB | Without provenance | Details for kevlar-0.0.8.tar.gz |
Release files / kevlar-0.0.8.tar.gz
| Download URL | kevlar-0.0.8.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c76a4e81928986e3e9842e9e8df235917bd9043b6e6bbbd48ab7e9836be86691
|
|
BLAKE2b-256 checksum How to use checksums |
09a819047813283cf6ead2621f942bd776c8e7f14d854d3c917f24829a516c08
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for kevlar 0.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.