Coverage Tracking
See Exactly Which API Endpoints Are Tested — and Which Aren't
Most teams can't answer "what percentage of our API is tested?" Shift-Left API shows you coverage per endpoint, including status codes, parameters and request-body fields.
The coverage visibility problem
Blind spots everywhere
You have tests, but you can't tell which endpoints are covered and which have zero test cases.
Code coverage misses the point
Server-side code coverage tells you lines executed, not which API operations are tested.
New endpoints go untested
New API endpoints ship without tests. Nobody tracks what was added vs. what was tested.
Status codes are ignored
Tests cover the 200 response but skip 400, 401, 403, 404, and 500 scenarios.
Parameter coverage is unknown
Query parameters, headers, and request body fields — you don't know which combinations are tested.
Coverage trends are invisible
Is coverage improving or degrading across releases? Without tracking, you're guessing.
Why existing tools don't track API coverage
Most API testing tools tell you if tests passed. They don't tell you what isn't tested.
How API coverage tracking works in Shift-Left API
Import your OpenAPI spec
The platform maps every endpoint, method, status code, and parameter from your specification.
Generate tests and see coverage
AI generates tests and the coverage dashboard immediately shows what's covered and what's not.
Fill gaps with one click
Click on uncovered endpoints or status codes to generate targeted tests. Close every gap your project settings allow, without manual work.
Track trends in CI/CD
Run results are reported on every pipeline run. Set a pass-rate threshold so the build fails when tests fall short.
Per endpoint
Status codes, parameters, request body
1 click
Generate tests for gaps
Per build
Coverage in CI/CD reports
Trends
Coverage over time
Enterprise readiness
What procurement, security, and platform-engineering ask for when coverage tracking is part of an audit-ready release process.
Role-based access
Five built-in roles with project-scoped assignment. Coverage data and gap-fill actions gated per role; every action captured in the audit log.
Audit-ready evidence
CI runs write JUnit XML and a JSON summary, and the audit log records changes to tests, endpoints and settings.
On-prem and self-hosted
Coverage tracking runs inside your infrastructure on a self-hosted install, and AI-driven gap-fill can use your self-hosted LLM (Trial and Enterprise). Licence validation and updates contact Total Shift Left; ask us about offline licensing for air-gapped installs.
Quality gate enforcement
The quality gate fails the build when the pass rate falls below your threshold or any test ends in error, and you choose whether a missed gate fails or warns.
Data residency
Coverage metrics, captured payloads, and run reports stay in the region your deployment runs in. Self-hosted keeps data with you; the cloud SaaS has no region choice today.
Regulated industries fit
Self-hosting, per-project roles and the audit log support the controls regulated teams review. This is not a certification. See the regulated-industries pages for sector-specific framing.
For deployment topology see the deployment page; for the data-flow and access-control posture see platform security.
Frequently asked questions
What types of API coverage does Shift-Left API track?
Coverage is measured against your spec: status codes, parameters and request-body fields per endpoint, plus auth, routing, schema and error-body checks, with gaps you can fill in one click.How is this different from code coverage?
Code coverage (Istanbul, JaCoCo) measures which lines of server code are executed. API coverage measures which API operations — endpoints, methods, status codes, and parameters — have test cases. You need both for complete quality visibility.Can I generate tests for uncovered areas?
Yes. Click on any uncovered endpoint, method, or status code in the dashboard, and the AI generates targeted tests to fill the gap. One click, no scripting.Does coverage integrate with CI/CD?
Yes. Run results are included in pipeline reports. The quality gate fails the build when the pass rate falls below your threshold or any test ends in error, and you choose whether a missed gate fails or warns.Can I track coverage across multiple services?
Yes. Each microservice has its own project and coverage dashboard. You can view coverage per service or across all services from a unified dashboard.What do I get when I import a spec?
Generation plans 79 scenario classes across 12 dimensions without an AI key, and 'Generate tests for gaps' closes every gap your project settings allow.
Generate your first API test suite in minutes
Import your OpenAPI spec. Get CI-ready tests. Track coverage. No code, no credit card, 15-day free trial.