QE Contract Testing

Automate API contract testing for REST, GraphQL, and event-driven systems.

1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/aquariuscook/Agent_Modus_Map --skill qe-contract-testing-aquariuscook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: QE Contract Testing
Source: https://github.com/aquariuscook/Agent_Modus_Map/tree/main/.claude/skills/qe-contract-testing
Command: npx skills add https://github.com/aquariuscook/Agent_Modus_Map --skill qe-contract-testing-aquariuscook

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of ensuring that APIs adhere to their defined contracts, preventing integration issues and ensuring backward compatibility.

Core Features & Use Cases

  • Consumer-Driven Contract Testing: Validate API interactions based on consumer expectations using tools like Pact.
  • Schema Validation: Verify API requests and responses against OpenAPI or other schema definitions.
  • Breaking Change Detection: Identify potential compatibility issues between API versions.
  • GraphQL & Event Contract Testing: Extend contract testing to GraphQL APIs and event-driven systems.
  • Use Case: Before deploying a new version of a microservice, use this Skill to verify that it still meets the contract requirements of all its consumers and that no breaking changes have been introduced.

Quick Start

Use the qe-contract-testing skill to verify the provider at http://localhost:3000 against contracts located in the contracts/ directory.

Frequently Asked Questions about QE Contract Testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate API contract testing for microservices before deployment?

You can validate consumer-driven contracts using tools like Pact to verify that API interactions meet consumer expectations and maintain backward compatibility across microservices.

What is the best way to detect breaking changes between API versions?

Detect breaking changes between API versions by comparing new provider responses against established contracts and OpenAPI schema definitions, ensuring no incompatible modifications reach production.

Does contract testing work with GraphQL APIs and event-driven systems?

Contract testing supports GraphQL APIs and event-driven systems by validating schema adherence and interaction contracts, extending quality assurance beyond standard REST API endpoints.

How do I validate API responses against an OpenAPI schema definition?

Validate API requests and responses against OpenAPI schema definitions by automating checks that verify provider outputs match the documented contract, ensuring strict schema adherence.

Can I integrate consumer-driven contract verification into my CI/CD pipeline?

You can integrate contract testing into CI/CD pipelines to automatically verify provider endpoints against stored contracts, ensuring robust API quality assurance is executed on every code change.