What problem does it solve? After implementing or modifying API endpoints, developers need a fast way to validate the deployed HTTP contract end-to-end without writing heavy integration test suites. This Skill provides a repeatable workflow for authoring and executing Bruno CLI test collections against a locally running backend as a post-implementation smoke and E2E validation step. ## Core Features & Use Cases - Bruno Collection Authoring: Create .bru request files with assertions and test blocks covering happy paths, validation errors, not-found, and conflict scenarios. - CLI Test Execution: Run entire collections, single module folders, or individual request files with bru run against a configurable local environment. - Full Workflow Integration: Start the Spring Boot app, wait on the health endpoint, run tests, interpret failures (max 3 attempts), and shut the app down cleanly. - Use Case: After adding a new /api/v1/locations endpoint, generate Bruno requests for create, validation-error, and duplicate cases, then run bru run api-tests/locations/ --env local to verify the live API contract. ## Quick Start Run the Bruno API tests for the endpoints I just changed by starting the app, executing bru run against the api-tests collection with the local environment, and reporting any failures.
