[API Testing]
API Contract Testing Intensive
We model producer and consumer responsibilities, craft OpenAPI-backed tests, and explore failure injection that still respects staging data policies. Workshops include negotiating versioning with backend teams and writing dashboards that show contract drift before deploy windows.
Included focus areas
- Schema diff workflows with breaking-change callouts
- Negative testing matrices that stay readable for PMs
- Synthetic data guardrails for shared environments
- Pairing templates for backend engineers
- Lightweight dashboards in Grafana or Datadog (choose one track)
- Postman/Newman and code-first samples side by side
- Runbooks for when contracts fail mid-release
Outcomes you can demonstrate
- Stand up a contract suite covering three critical endpoints for the practice service
- Facilitate a versioning conversation using shared language from the course
- Document observability signals that should accompany contract failures
Facilitator
Riley Ng
API testing coach focused on payment gateways and logistics integrations.
FAQ
GraphQL coverage?
We touch GraphQL introspection pitfalls in one session, but REST and JSON-first contracts receive the majority of lab time.
Hardware requirements?
A machine capable of running Docker for mock services is recommended; cloud IDs can be provided with limited hours.
What is excluded?
We do not supply production API keys or access to your employer systems; all work happens in provided sandboxes.
Participant notes
The negative matrix template now travels with every release ticket. Still adapting it for GraphQL, but the REST portion is battle-tested.