Learn the vocabulary of schema validation in API testing: JSON Schema, OpenAPI contract validation, breaking changes, and schema drift.
0 / 5 completed
1 / 5
A test failure message says 'the response doesn't match the schema'. What does this mean?
Schema validation failures mean the actual API response (field names, types, required fields, formats) doesn't conform to the contract defined in the schema, indicating a potential breaking change.
2 / 5
What is 'breaking change detection' in API contract testing?
Breaking change detection tools compare two versions of an API schema and flag changes that would break consumers: removed fields, changed types, new required fields, or renamed endpoints.
3 / 5
What does 'schema drift' mean in an API context?
Schema drift occurs when the live API implementation gradually diverges from its documented schema without intentional versioning — a common problem when documentation isn't updated alongside code changes.
4 / 5
What is 'OpenAPI contract validation' in an integration test?
OpenAPI contract validation means making real HTTP requests and comparing the responses (status codes, headers, body structure) against the API's OpenAPI spec to ensure implementation matches documentation.
5 / 5
In JSON Schema, what does the `required` keyword validate?
The `required` keyword in JSON Schema is an array of property names that must be present in the object. Validation fails if any listed property is missing from the actual response.