What problem does it solve?
Route testing becomes slow and error-prone when endpoints require authenticated cookie-based JWTs, especially during debugging of 401/403 failures and verification of request/response behavior.
Core Features & Use Cases
- Cookie-based JWT authentication for tests: Uses a refresh_token cookie (Keycloak-issued) instead of Bearer headers, matching your real auth flow.
- One-command route verification: Generates an authenticated request, prints response status/body, and provides a reproducible curl command.
- Environment-aware options (recommended vs mock): Supports Keycloak-backed testing via test-auth-route.js and offers development-only mock authentication patterns for fast iteration.
- Use Case: After changing an endpoint, run a POST test with the expected payload, then immediately validate the authenticated response and (optionally) confirm related database effects.
Quick Start
Use the route-tester skill to test an authenticated endpoint by running the provided test-auth-route.js command against your full route URL with the expected HTTP method and JSON body.