Postman API Testing(EN)
Need outputs that should land in a Postman API testing workflow.
StatusStable
TypeAtomic Skill
DomainSoftware testing
SDLCTest design
Good forQA / DEV
LanguageChinese / English
EvalsEvals ✓
Synced2026-09-15
Why this Skill
It turns this Skill's method into a quality input that can be executed, reviewed, and reused.
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
When to use
Use this Skill
- Need outputs that should land in a Postman API testing workflow.
- The project already uses Postman or wants Postman-ready planning.
Common pitfalls
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
- Do not skip assumptions and missing information.
Input
Minimum Input
- Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
Recommended Input
- Project goal
- Test scope
- Constraints
Optional Context
- Relevant code or configuration
- Historical results
- Logs and metrics
Output
The output follows this Skill's method and makes facts, assumptions, risks, and next steps explicit.
These are the Skill's expected output requirements, not evidence that it ran in a real project.
- 01Open prompts/api-test-postman.md and use it as the main prompt.
- 02Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
- 03If the input is incomplete, return a usable first version and mark missing information and assumptions.
How It Works
- 01Open prompts/api-test-postman.md and use it as the main prompt.
- 02Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
- 03If the input is incomplete, return a usable first version and mark missing information and assumptions.
Install & Quick Start
Install command / SHELL
npx skills add \
https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-test-postman
-gapi-test-postman.prompt
@skill api-test-postman
Using the current project context, produce an actionable result following this Skill.
Additional context:
[Paste project context or requirement]---
name: api-test-postman
description: Use this skill when you need to design Postman collections, environments, scripts, and Newman-ready API regression plans; triggers include Postman API testing, API testing, and api-test-postman.
---
# Postman API Testing (EN)
**Chinese version：** See the corresponding Chinese skill.
## When to Use
- Need outputs that should land in a Postman API testing workflow.
- The project already uses Postman or wants Postman-ready planning.
## Output Format Options
Markdown by default unless the request explicitly asks for another format.
## How to Use
1. Open `prompts/api-test-postman.md` and use it as the main prompt.
2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
3. If the input is incomplete, return a usable first version and mark missing information and assumptions.
## Reference Files
- `prompts/api-test-postman.md`: main prompt for this skill.
- `references/framework-spec.md`: tool-specific structure and coverage notes.
- `references/setup-and-ci.md`: setup, execution, and CI notes.
- `examples/sample-context.md`: sample request context.
- `scripts/run-tests.sh`: lightweight local execution entry point.
## Common Pitfalls
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
- Do not skip assumptions and missing information.
## Best Practices
- Start from the prompt file, then add only the context that matters.
- Keep the output risk-driven and executable.
- If the request is incomplete, return a usable first version and mark gaps.