Declarative API testing in Treseko 1.0.6
Define API requests and assertions through a reviewable contract, with destination allowlists and redacted evidence.
This page is part of Treseko public resources for quality management, automation, evidence and release decisions.
Declare the test, then verify the result
An API test defines its request, input data, and response conditions. The contract makes the check visible without relying on credentials pasted into a script nobody wants to maintain.
An allowlist limits permitted destinations, and snapshots redact sensitive values before persistence. Manual and automated execution follow different routes, each with its own controls.
A 200 is not an automatic gold star
HTTP status is only one part of the result: assertions over status, headers, or body must also pass. Scripts and inline secrets should not be invented as substitutes for the declared contract.
The technical guide covers treseko.api-test/v1, its limits, and how to review an execution.
Explore each capability
View documentation · Explore QA solutions · Browse QA resources