smoke-test

Generate chainable curl scripts for API smoke testing by scanning controller source files to extract endpoints, routes, and DTOs. The resulting self-contained bash script executes create, read, update, business action, and cleanup steps sequentially.

Controller scanning parses backend module source files to extract HTTP endpoints, route patterns, DTOs, and validation rules. This extracted metadata is then used to construct chainable curl requests that validate end-to-end CRUD and business flows.

Yes, you can automate end-to-end API testing using bash and curl. The generated script reads AI_ACCESS_KEY and SMOKE_TEST_HOST from the environment, applies header authentication, and passes extracted IDs between requests using jq.

The best way to automate CRUD smoke tests is generating a self-contained bash script with module-specific sequences for automations, users, and logs. It chains curl requests for create, read, update, and cleanup while maintaining observability and clear failure messages.

Yes, the smoke test script handles authentication by reading AI_ACCESS_KEY and SMOKE_TEST_HOST from your environment variables. It emits header-based authentication automatically and provides clear observability for production safety.

Pass extracted IDs between curl requests in a bash smoke test by using jq to parse JSON responses. The chainable script extracts the necessary identifiers from create operations and passes them to subsequent read, update, and cleanup steps.