TraceCov
Schema-level API coverage down to individual keywords.
Your API tests pass. But did you actually test the validation rules?
Hitting POST /users with {"name": "Alice", "age": 30} gives you 100% endpoint coverage—but you haven't tested empty names, negative ages, or strings that are too long.
TraceCov measures coverage at the schema keyword level: minLength, pattern, enum, minimum - not just endpoints.
Install
pip install tracecov
Quick Start
import tracecov
import requests
# Load your OpenAPI schema
coverage = tracecov.CoverageMap.from_path("openapi.json")
# Wrap your session to track requests
session = coverage.requests.track_session(requests.Session())
# Run your tests as usual
session.post("https://api.example.com/users", json={"name": "Alice"})
session.get("https://api.example.com/users/123")
# Generate the report
coverage.save_report()
What It Tracks
| Dimension | What it measures |
|---|---|
| Operations | HTTP method + path combinations called |
| Parameters | Path, query, header, cookie, body coverage |
| Keywords | JSON Schema validation rules (minLength, pattern, etc.) |
| Examples | Schema examples and defaults used |
| Responses | HTTP status codes returned |
Documentation
Feedback
Help shape TraceCov: 2-minute survey
Professional Edition
For advanced features, contact info@tracecov.sh.
1 maintainer
Metadata
1 maintainer
Release files for tracecov 0.25.5
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 | |
|---|---|---|---|---|
| tracecov-0.25.5.tar.gz | 22.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tracecov-0.25.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.7 kB
Release files / tracecov-0.25.5.tar.gz
| Download URL | tracecov-0.25.5.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee246f7e426fe34fddd0c70f8067888f6a8d7e3daf73d904932b2cfddc25956e
|
|
BLAKE2b-256 checksum How to use checksums |
1c7d2b768e14b5b90a3746445cbf82a7a12a39afcedeaa2378ff9ee772d29220
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tracecov-0.25.5-py3-none-any.whl
| Download URL | tracecov-0.25.5-py3-none-any.whl |
|---|---|
| Size | 29.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
88db4fe80c37b7b51da4dc6071935d1876e705074b73f41a1e06fc9390b07dd4
|
|
BLAKE2b-256 checksum How to use checksums |
65afb3b02feda339876079ebebea967921f6f47bed0185f1260c1b570febd748
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tracecov 0.25.5
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.
