Saltar al contenido
SDETRole
SDETRole

Testing de APIs

Plantillas de casos de prueba de API REST

Genera un checklist estructurado de pruebas de API REST para un endpoint.

Se ejecuta íntegramente en tu navegador Sin registro

Endpoint

Use {id} or :id for path parameters.

Used in titles.

Endpoint characteristics

Test cases · 25

  1. TC-001PositiveP1

    POST order succeeds with valid input

    Steps

    1. Send POST /api/v1/orders with a valid token and a valid request body.
    2. Capture status, headers and body.

    Expected

    201 Created (or 200/202 if documented). Response body matches the documented schema; Content-Type is correct (e.g. application/json).

  2. TC-002PositiveP1

    Created order is persisted and retrievable

    Steps

    1. Send POST /api/v1/orders with a valid body.
    2. Read the Location header or returned id.
    3. GET the created order.

    Expected

    Location (if returned) points to the new order; GET returns the same field values that were sent, plus server-generated fields (id, timestamps).

  3. TC-003NegativeP2

    Unsupported method returns 405

    Steps

    1. Send an HTTP method the endpoint does not support to /api/v1/orders.

    Expected

    405 Method Not Allowed with an Allow header listing the supported methods.

  4. TC-004NegativeP1

    Malformed JSON body is rejected

    Steps

    1. Send POST /api/v1/orders with invalid JSON (e.g. a trailing comma).

    Expected

    400 Bad Request with a clear parse error. Never 500.

  5. TC-005NegativeP2

    Wrong Content-Type is rejected

    Steps

    1. Send POST /api/v1/orders with a valid body but Content-Type: text/plain.

    Expected

    415 Unsupported Media Type (or 400 if documented).

  6. TC-006NegativeP3

    Unacceptable Accept header

    Steps

    1. Send POST /api/v1/orders with Accept: application/xml (if only JSON is supported).

    Expected

    406 Not Acceptable, or JSON returned anyway if the API ignores Accept. Behaviour should be consistent and documented.

  7. TC-007AuthP1

    Missing credentials returns 401

    Steps

    1. Send POST /api/v1/orders without an Authorization header.

    Expected

    401 Unauthorized with a WWW-Authenticate header. No data leaked in the body.

  8. TC-008AuthP1

    Invalid or expired token returns 401

    Steps

    1. Send POST /api/v1/orders with a malformed token, then with an expired token.

    Expected

    401 Unauthorized in both cases.

  9. TC-009AuthP1

    Insufficient permissions return 403

    Steps

    1. Send POST /api/v1/orders as a user without the required role or scope.

    Expected

    403 Forbidden. No side effects (nothing created, changed or deleted).

  10. TC-010ValidationP1

    Each required field is enforced

    Steps

    1. For each required field, send the body with that field removed.

    Expected

    400 Bad Request (or 422) naming the missing field. One case per field.

  11. TC-011ValidationP1

    Wrong data types are rejected

    Steps

    1. For each field, send a value of the wrong type (string for number, number for string, object for array).

    Expected

    400/422 naming the field. Values are not silently coerced unless documented.

  12. TC-012ValidationP2

    Null and empty values

    Steps

    1. Send null, "" and whitespace-only strings for required fields.

    Expected

    400/422 for required fields; optional fields accept null only if documented.

  13. TC-013ValidationP2

    Unknown properties are handled

    Steps

    1. Add an unexpected property to the body.

    Expected

    Either rejected with 400 or ignored, matching the API contract. Never stored or echoed back.

  14. TC-014ValidationP2

    Mass assignment of protected fields

    Steps

    1. Send server-controlled fields such as id, role, isAdmin, createdAt or balance in the body.

    Expected

    Values are ignored or rejected; protected fields keep their server-side values.

  15. TC-015BoundaryP2

    String length limits

    Steps

    1. For each length-limited field, send min-1, min, max and max+1 characters.

    Expected

    min and max accepted; min-1 and max+1 rejected with 400/422.

  16. TC-016BoundaryP2

    Numeric range limits

    Steps

    1. For each numeric field, send minimum-1, minimum, maximum, maximum+1, 0 and a negative value.

    Expected

    Values inside the range accepted; outside rejected with 400/422. No overflow or 500.

  17. TC-017BoundaryP3

    Unicode and special characters

    Steps

    1. Send names containing accents, emoji, RTL text, quotes and <script> tags.

    Expected

    Stored and returned unchanged (correct UTF-8), and never executed or reflected unescaped.

  18. TC-018BoundaryP3

    Oversized payload

    Steps

    1. Send a body larger than the documented limit.

    Expected

    413 Content Too Large, not a timeout or 500.

  19. TC-019IdempotencyP2

    Duplicate submission behaviour

    Steps

    1. Send POST /api/v1/orders twice quickly with the same body.

    Expected

    Behaviour matches the contract: either two records, or a 409 Conflict on a unique field. No partial or corrupted record.

  20. TC-020Rate limitP2

    Exceeding the rate limit returns 429

    Steps

    1. Send POST /api/v1/orders repeatedly until the documented limit is exceeded.

    Expected

    429 Too Many Requests with a Retry-After header; requests succeed again after waiting.

  21. TC-021Rate limitP3

    Rate limit headers are accurate

    Steps

    1. Send POST /api/v1/orders and read the rate limit headers (RateLimit / X-RateLimit-*).

    Expected

    Remaining count decreases by one per request and resets at the advertised time.

  22. TC-022Security headersP2

    Security and cache headers are present

    Steps

    1. Send POST /api/v1/orders with a valid token and inspect response headers.

    Expected

    Strict-Transport-Security and X-Content-Type-Options: nosniff are present; Cache-Control: no-store on authenticated responses; no Server/X-Powered-By version disclosure.

  23. TC-023Security headersP3

    CORS policy is restrictive

    Steps

    1. Send POST /api/v1/orders with Origin: https://evil.example.

    Expected

    Access-Control-Allow-Origin is absent or not reflecting the untrusted origin; never "*" together with credentials.

  24. TC-024Security headersP2

    Errors do not leak internals

    Steps

    1. Trigger a 4xx and (if possible) a 5xx response.

    Expected

    Error bodies contain no stack traces, SQL, file paths or framework versions.

  25. TC-025Performance smokeP3

    Response time within budget

    Steps

    1. Send POST /api/v1/orders 10 times sequentially and record durations.

    Expected

    p95 under the agreed budget (for example 500 ms); no request times out.

Acerca de esta herramienta

La mayoría de los planes de prueba de API se olvidan de lo mismo: autorización a nivel de objeto, reintentos idempotentes, extremos de la paginación, cabeceras de rate limit y bodies de error que filtran detalles internos. Describe un endpoint (método, ruta, si requiere autenticación, si recibe body, si está paginado, si acepta un Idempotency-Key o si tiene rate limit) y esta herramienta aplica un conjunto fijo de reglas para producir un checklist numerado con prioridad, pasos y resultado esperado para cada caso. La salida es determinista: el mismo endpoint genera siempre los mismos ID, lo que mantiene estables los casos exportados cuando los regeneras. Tómalo como punto de partida y añade las reglas de negocio que solo tú conoces.

Cómo usarla

  1. Elige el método e introduce la ruta. Usa {id} o :id para los parámetros de ruta, así se añaden los casos de recurso no encontrado y de control de acceso.
  2. Marca las características que aplican al endpoint.
  3. Revisa el checklist, fíltralo por categoría si hace falta, y cópialo o descárgalo como tabla Markdown o CSV para tu herramienta de gestión de pruebas.

Preguntas frecuentes: Plantillas de casos de prueba de API REST

¿Qué es BOLA (o IDOR) y por qué es P1?

Broken Object Level Authorisation significa que un usuario puede acceder al objeto de otro usuario cambiando un id en la petición. Es el riesgo número uno del OWASP API Security Top 10 porque es común y fácil de explotar, así que todo endpoint con un id en la ruta debería tener esta prueba.

¿Por qué no hay casos de clave de idempotencia para PUT o DELETE?

RFC 9110 define PUT y DELETE (y GET) como idempotentes, así que repetirlos debe tener el mismo efecto sin necesidad de clave. Para ellos la herramienta añade en su lugar un caso de “repeat the request”. Idempotency-Key es relevante para POST y PATCH.

¿Puedo importar el CSV en Jira, TestRail o Xray?

El CSV tiene las columnas ID, Category, Priority, Title, Steps y Expected result con comillas estándar, así que la mayoría de los asistentes de importación pueden mapearlo. Tendrás que asignar las columnas a los campos de tu herramienta durante la importación.

Escribe para buscar en todo SDETRole.

Búsqueda de texto completo con Pagefind · se ejecuta en tu navegador Abrir la página de búsqueda →