Contract testing templates
Copy a ready-made portman-config.json for a common use case, point it at your spec, and run.
Baseline contract tests
Start contract testing every operation in your spec with one rule.
Strict response validation
Catch undocumented response fields, wrong content types and missing headers.
Response time budget
Fail the run when endpoints respond slower than an agreed budget.
Auth token chaining
Get an access token from a token endpoint and use it for every other request.
CRUD flow chaining
Create a record, then read, update and delete that same record.
Negative testing with variations
Verify that bad credentials and invalid input return the documented 4xx errors.
Fuzz create and update requests
Automatically probe validation with missing fields and out-of-range values.
Response content assertions
Check that responses contain specific values, not just the right shape.
Read-only smoke tests
Test only safe GET operations, for example against production.
Pre-request script setup
Prepare dynamic data before requests run, from iteration data or computed values.