Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/api-testing:validate-contractsThe summary Claude sees in its command listing — used to decide when to auto-load this command
# validate-contracts Set up consumer-driven contract testing ## Chains 1. **contract-testing** — Implement contracts 2. **api-test-plan** — Plan testing 3. **schema-validation** — Validate schemas ## Usage ## Expected Output - Comprehensive analysis or plan - Actionable recommendations - Implementation steps - Success criteria ---
Set up consumer-driven contract testing
/validate-contracts "Describe your testing need"
npx claudepluginhub sethdford/claude-skills --plugin qa-api-testing/contract-testValidates API contracts with Pact consumer-driven testing and OpenAPI specs, generates tests, detects breaking changes, and outputs a detailed testing report.
/generate-contractGenerates API contracts for consumer-driven contract testing in Pact, Spring Cloud Contract, and OpenAPI formats with verification tests and CI/CD setup.
/api-contract-testerTests API contracts via Pact consumer/provider, Postman collections, OpenAPI/GraphQL schemas. Validates compatibility, detects breaking changes, generates reports.
/test-apiDesign comprehensive API testing strategy including contracts and integration tests.
/create-contractCreates Pact contract test for consumer-driven API testing: prompts for consumer/provider names, defines interactions with matchers and states, runs test to generate validated JSON contract file in pacts directory.
/contractsExtracts, defines, and validates API contracts (payloads, models, events) as concrete schema files from specs, with support for validation, sync, listing, and multiple output formats.