qe-contract-testing
Consumer-driven contract testing for APIs including REST, GraphQL, and event-driven systems with schema validation.
Best use case
qe-contract-testing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Consumer-driven contract testing for APIs including REST, GraphQL, and event-driven systems with schema validation.
Teams using qe-contract-testing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/qe-contract-testing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How qe-contract-testing Compares
| Feature / Agent | qe-contract-testing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Consumer-driven contract testing for APIs including REST, GraphQL, and event-driven systems with schema validation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# QE Contract Testing
## Purpose
Guide the use of v3's contract testing capabilities including consumer-driven contracts, schema validation, backward compatibility checking, and API versioning verification.
## Activation
- When testing API contracts
- When validating schema changes
- When checking backward compatibility
- When testing GraphQL APIs
- When verifying event schemas
## Quick Start
```bash
# Generate contract from API
aqe contract generate --api openapi.yaml --output contracts/
# Verify provider against contracts
aqe contract verify --provider http://localhost:3000 --contracts contracts/
# Check breaking changes
aqe contract breaking --old api-v1.yaml --new api-v2.yaml
# Test GraphQL schema
aqe contract graphql --schema schema.graphql --operations queries/
```
## Agent Workflow
```typescript
// Contract generation
Task("Generate API contracts", `
Analyze the REST API and generate consumer contracts:
- Parse OpenAPI specification
- Identify critical endpoints
- Generate Pact contracts
- Include example requests/responses
Output to contracts/ directory.
`, "qe-api-contract")
// Breaking change detection
Task("Check API compatibility", `
Compare API v2.0 against v1.0:
- Detect removed endpoints
- Check parameter changes
- Verify response schema changes
- Identify deprecations
Report breaking vs non-breaking changes.
`, "qe-api-compatibility")
```
## Contract Testing Types
### 1. Consumer-Driven Contracts (Pact)
```typescript
await contractTester.consumerDriven({
consumer: 'web-app',
provider: 'user-service',
contracts: 'contracts/web-app-user-service.json',
verification: {
providerBaseUrl: 'http://localhost:3000',
providerStates: providerStateHandlers,
publishResults: true
}
});
```
### 2. Schema Validation
```typescript
await contractTester.validateSchema({
type: 'openapi',
schema: 'api/openapi.yaml',
requests: actualRequests,
validation: {
requestBody: true,
responseBody: true,
headers: true,
statusCodes: true
}
});
```
### 3. GraphQL Contract Testing
```typescript
await graphqlTester.testContracts({
schema: 'schema.graphql',
operations: 'queries/**/*.graphql',
validation: {
queryValidity: true,
responseShapes: true,
nullability: true,
deprecations: true
}
});
```
### 4. Event Contract Testing
```typescript
await contractTester.eventContracts({
schema: 'events/schemas/',
events: {
'user.created': {
schema: 'UserCreatedEvent.json',
examples: ['examples/user-created.json']
},
'order.completed': {
schema: 'OrderCompletedEvent.json',
examples: ['examples/order-completed.json']
}
},
compatibility: 'backward'
});
```
## Breaking Change Detection
```yaml
breaking_changes:
always_breaking:
- endpoint_removed
- required_param_added
- response_field_removed
- type_changed
potentially_breaking:
- optional_param_removed
- response_field_added
- enum_value_removed
non_breaking:
- endpoint_added
- optional_param_added
- response_field_made_optional
- documentation_changed
```
## Contract Report
```typescript
interface ContractReport {
summary: {
contracts: number;
passed: number;
failed: number;
warnings: number;
};
consumers: {
name: string;
contracts: ContractResult[];
compatibility: 'compatible' | 'breaking' | 'unknown';
}[];
breakingChanges: {
type: string;
location: string;
description: string;
impact: 'high' | 'medium' | 'low';
migration: string;
}[];
deprecations: {
item: string;
deprecatedIn: string;
removeIn: string;
replacement: string;
}[];
}
```
## CI/CD Integration
```yaml
contract_verification:
consumer_side:
- generate_contracts
- publish_to_broker
- can_i_deploy_check
provider_side:
- fetch_contracts_from_broker
- verify_against_provider
- publish_results
pre_release:
- check_breaking_changes
- verify_all_consumers
- update_compatibility_matrix
```
## Pact Broker Integration
```typescript
await contractTester.withBroker({
brokerUrl: 'https://pact-broker.example.com',
auth: { token: process.env.PACT_TOKEN },
operations: {
publish: true,
canIDeploy: true,
webhooks: true
}
});
```
## Coordination
**Primary Agents**: qe-api-contract, qe-api-compatibility, qe-graphql-tester
**Coordinator**: qe-contract-coordinator
**Related Skills**: qe-test-generation, qe-security-complianceRelated Skills
qe-visual-testing-advanced
Advanced visual regression testing with pixel-perfect comparison, AI-powered diff analysis, responsive design validation, and cross-browser visual consistency. Use when detecting UI regressions, validating designs, or ensuring visual consistency.
qe-shift-right-testing
Testing in production with feature flags, canary deployments, synthetic monitoring, and chaos engineering. Use when implementing production observability or progressive delivery.
qe-shift-left-testing
Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix. Use when implementing TDD, CI/CD, or early quality practices.
qe-security-visual-testing
Security-first visual testing combining URL validation, PII detection, and visual regression with parallel viewport support. Use when testing web applications that handle sensitive data, need visual regression coverage, or require WCAG accessibility compliance.
qe-security-testing
Test for security vulnerabilities using OWASP principles. Use when conducting security audits, testing auth, or implementing security practices.
qe-risk-based-testing
Focus testing effort on highest-risk areas using risk assessment and prioritization. Use when planning test strategy, allocating testing resources, or making coverage decisions.
qe-regression-testing
Strategic regression testing with test selection, impact analysis, and continuous regression management. Use when verifying fixes don't break existing functionality, planning regression suites, or optimizing test execution for faster feedback.
qe-performance-testing
Test application performance, scalability, and resilience. Use when planning load testing, stress testing, or optimizing system performance.
qe-observability-testing-patterns
Observability and monitoring validation patterns for dashboards, alerting, log aggregation, APM traces, and SLA/SLO verification. Use when testing monitoring infrastructure, dashboard accuracy, alert rules, or metric pipelines.
qe-n8n-workflow-testing-fundamentals
Comprehensive n8n workflow testing including execution lifecycle, node connection patterns, data flow validation, and error handling strategies. Use when testing n8n workflow automation applications.
qe-n8n-trigger-testing-strategies
Webhook testing, schedule validation, event-driven triggers, and polling mechanism testing for n8n workflows. Use when testing how workflows are triggered.
qe-n8n-security-testing
Credential exposure detection, OAuth flow validation, API key management testing, and data sanitization verification for n8n workflows. Use when validating n8n workflow security.