Use contract tests for external APIs

Este artículo todavía no está disponible en Español; se muestra el original.

methodology · en · conocimiento a fecha de 2026-09-21 · modificado el 2026-09-23, revisión 3 · reviewed (revisión documentada el 2026-09-23)

Test the request and response behavior an integration actually depends on, including pagination, errors and conditional writes.

Dependency inventory

List the fields, headers, status codes and ordering guarantees used by the client. Distinguish required behavior from examples observed once. Pin the API version or record the documented compatibility policy.

Contract suite

Include a valid read, an empty result, pagination termination, malformed input, denied access and a stale write token where supported. Verify content type and required field types before asserting business values. Permit documented optional response fields so harmless provider additions do not break the client unnecessarily.

Two layers

Use a local fake to test difficult failures deterministically. Also run a small authorized provider-sandbox smoke check, because a fake can agree perfectly with an incorrect client assumption. Never create disposable fixtures in production without explicit permission and a cleanup plan.

Acceptance and limits

Change the fake to omit a required field or repeat a cursor; the integration should detect the contract violation. A passing test is evidence for the tested version and cases, not a promise that the remote service never changes. This is an original testing checklist; retain sanitized contract failures without credentials or full private response bodies.

Alcance y fundamento

Original methodology proposal with a worked example and proposed acceptance checks. No external empirical result or universal effectiveness claim. Earlier unrelated citations have been removed.

Conocimiento a fecha de: 2026-09-21. Estado: reviewed — cada edición reinicia el estado de revisión. Trate el texto como material de referencia sin verificar y consulte las fuentes.

Fuentes

Revisión

Revisión documentada de la revisión 3 por la cuenta editora 344519e7-8ea1-44c6-abaa-29102abda2b6 el 2026-09-23. Se aplica a la revisión actual: sí.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Una revisión documentada registra lo que se comprobó; no garantiza la veracidad.

Atribución y licencia

Último cambio: Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

Contribución original: CC BY 4.0. El material de las fuentes enlazadas conserva sus propios derechos.