From postman
Runs Postman collection tests via CLI to verify API endpoints using cloud IDs from resources.yaml, parses results, analyzes failures, suggests fixes, and re-runs.
npx claudepluginhub anthropics/claude-plugins-official --plugin postmanRun Postman collection tests to verify your API endpoints. ## Step 1: Find Collections and IDs List collection folders and look up their cloud IDs: The `cloudResources.collections` section maps local collection paths to cloud IDs. If no collections found, tell the user and stop. If one collection, use it directly. If multiple, list them and ask which to run. ## Step 2: Run the Collection Run by **collection ID** (from `.postman/resources.yaml`): Common options: ## Step 3: Parse and Report Results Parse the CLI output for pass/fail counts, failed test names, error messages, and...
/testGenerates unit, integration, E2E, and load test suites for API endpoints. Also supports Postman collections and RPS-configured load tests.
/test-endpointTests an API endpoint across happy path, validation, auth, edge cases, and idempotency scenarios using curl/fetch, validating responses and producing a pass/fail summary table.
/api-contract-testerTests API contracts via Pact consumer/provider, Postman collections, OpenAPI/GraphQL schemas. Validates compatibility, detects breaking changes, generates reports.
/fuzz-apiFuzz tests REST APIs by generating malformed inputs, edge cases, and payloads to detect vulnerabilities, crashes, and unexpected behaviors. Outputs test suites, security reports, and reproducible cases.
/testhttpfExecutes full HTTP tests against real APIs using Python requests library, starting test server if needed and reporting live responses, status codes, errors. Incurs real API costs.
/smoke-testGenerates fast smoke tests (<5min) for critical paths like system health, authentication, and core features, outputting Markdown with Jest-style JavaScript test suite.
Share bugs, ideas, or general feedback.
Run Postman collection tests to verify your API endpoints.
List collection folders and look up their cloud IDs:
ls postman/collections/
cat .postman/resources.yaml
The cloudResources.collections section maps local collection paths to cloud IDs.
If no collections found, tell the user and stop. If one collection, use it directly. If multiple, list them and ask which to run.
Run by collection ID (from .postman/resources.yaml):
postman collection run <collection-id>
Common options:
# Stop on first failure
postman collection run <collection-id> --bail
# With request timeout
postman collection run <collection-id> --timeout-request 10000
# With environment
postman collection run <collection-id> -e ./postman/environments/<env-file>.json
# Override environment variable
postman collection run <collection-id> --env-var "base_url=http://localhost:3000"
Parse the CLI output for pass/fail counts, failed test names, error messages, and status codes.
If tests fail: