Lesson 1
Status code is only transport evidence
A 200 response says little about whether the correct business outcome occurred.
All learning tracks
API & Integration QualityPractical 90 min
API Testing Beyond HTTP 200
Validate schemas, business invariants, negative paths, idempotency and downstream state instead of stopping at status codes.
RESTContractsNegative Testing
Learning outcomes
Build API risk scenarios
Validate state transitions
Test meaningful negative paths
Guided lessons
Learn the engineering thinking
Lesson 2
Schema and contract validation
Validate required fields, types, formats and compatibility because consumers depend on stable contracts.
Lesson 3
Business invariants
Test rules that must remain true across every request, such as totals, permissions, ownership and lifecycle constraints.
Lesson 4
Negative and boundary testing
Exercise malformed, missing, duplicated, unauthorised and out-of-range inputs intentionally.
Lesson 5
State transitions and side effects
Validate databases, events, downstream APIs and retries where a request causes broader system change.
Hands-on practice
Do something with what you learned
Do not just tick these mentally. Write the query, create the test matrix, refactor the code, or document the decision. Practical evidence is the point.