api-test

You can automate end-to-end API testing by starting the local server if needed and validating endpoints sequentially with curl, capturing complete responses to verify health, auth, and response formats without manual intervention.

A Test Execution Document (TED) is a comprehensive report generated in docs/reports/ that captures complete curl responses and validation results from sequential endpoint tests, providing structured documentation of your API testing execution.

Discover API endpoints by parsing OpenAPI specs or source routes directly during local development, allowing the testing process to identify and validate available endpoints automatically before running sequential curl checks.

Yes, API health checks can run without manual server startup because the testing process autonomously manages the server lifecycle, starting, monitoring, and cleaning up the local backend service as needed before validating endpoints.

Yes, this approach uses curl to validate endpoint authentication and response formats sequentially, capturing complete HTTP responses during local backend testing to ensure endpoints behave correctly and meet expected format requirements.

The best way to verify local backend endpoints during development is to automate sequential curl-based tests that handle server lifecycle management, perform health checks, and generate a structured Test Execution Document in docs/reports/.