x-execute-api-smoke-tests

Run automated REST API smoke tests by executing a Postman collection with Newman against your live deployment. This validates core endpoints and health checks in local, Kubernetes, or staging environments.

To run Newman smoke tests, you need Newman installed, a deployed application exposing a health endpoint, and a Postman collection located under smoke-tests/api/ with environment configurations.

Yes, you can run Postman health checks against Kubernetes deployments. The smoke tests support local, Kubernetes, and staging environments with optional port-forwarding to validate live endpoints.

The best way to validate core API endpoints after deployment is orchestrating black-box REST API smoke tests. This approach runs a Postman collection against live environments to verify health and core functionality.

REST API smoke testing creates isolated test data during each run to ensure idempotent testing. It collects structured results and gracefully handles failures without affecting subsequent test executions.

You should use Newman for REST API smoke testing because it orchestrates black-box tests against deployed environments, ensuring reliable validation of core endpoints and health checks with structured reporting and isolated test data.