API: New Endpoints in Latest Release
all
Persona: developer
Touchpoint: /api/new-endpoint-*
Preconditions
- Latest release deployed with new endpoints
- New endpoints documented in CHANGELOG
Steps
| # | Action | Expected Result |
|---|---|---|
| 1 | Check new endpoints are live | All new endpoints in release notes are accessible (not 404). |
| 2 | Test new endpoint with valid request | Returns 200 or expected status. Response includes documented fields. |
| 3 | Test new endpoint with invalid input | Returns 400 or appropriate error. No 500s or crashes. |
| 4 | Verify new endpoint auth | Auth required if documented as protected. Unauthenticated request rejected. |
| 5 | Check new endpoint latency | Response time <1s for non-async endpoints. Acceptable for use in frontend. |
| 6 | Verify new endpoint integrations | New endpoint calls other APIs correctly. No orphaned/missing dependencies. |
Known Failure Modes
- New endpoint returns 404 — not deployed
- New endpoint crashes on valid input — insufficient testing
- New endpoint missing auth — security gap
- New endpoint slow — frontend timeouts
References
- Playwright spec:
e2e (release validation) - Code files:
Notes
Run after each release to verify new API endpoints work end-to-end. Prevents shipping endpoints that are broken, slow, or missing auth. Tests are generated from CHANGELOG entries automatically if possible.