Api testing
Design and organize API tests (Postman/Newman, REST Assured, or similar). Use when building an API test suite or collection, including via an agent driving Postman. Covers structure, assertions, environments, and CI.From its SKILL.md
npx -y skills add vaibhavsaxena022/skills --skill api-testingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 204 tokens by cl100k_base, as published. Nobody here has run it
API Testing
Test the contract and the behavior, across environments, in CI.
Do
- Organize by resource/flow; use environments/variables for base URL, tokens, and ids.
- Assert status code and response schema/shape and key field values.
- Cover happy path, validation errors (4xx), auth failures, and edge inputs.
- Chain requests via captured variables (create → read → update → delete) and clean up after.
- Run collections headless in CI (Newman /
mvn) and gate merges on them. - Keep secrets in environment/secret stores.
Don't
- Don't hardcode tokens, ids, or hostnames into requests.
- Don't assert only on the status code — validate the body.
- Don't leave created data behind; clean up or use disposable data.
- Don't rely on a specific run order unless the flow genuinely requires it.
- Don't point tests at production without explicit intent.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.