What problem does it solve? Choosing and executing the right test level for a service treated as an independently deployable unit is hard: teams either over-test internals or ship with unverified inter-service contracts. This Skill defines how to verify a service's external behavior with stubbed dependencies, lock down inter-service API compatibility with consumer-driven contracts, and check structural conformance to OpenAPI/JSON Schema definitions. ## Core Features & Use Cases - Component Testing: Enumerate a service's public operations, stub only external dependencies, and verify representative success and failure cases with real internal logic. - Consumer-Driven Contract Testing (Pact): Fix the consumer's actual expectations as pact files, verify them in the provider's CI, and manage compatibility with a consumer/provider version matrix. - API Schema Validation: Validate real requests and responses against OpenAPI/JSON Schema using validators like Ajv, keeping implementation from drifting away from declared schemas. - Use Case: A team splitting a monolith into microservices uses this Skill to write Pact contracts for each cross-service call, run provider verification in CI, and confirm via can-i-deploy that no incompatible version pair ships. ## Quick Start Ask the AI to apply the levels-service testing guidance to design component and contract tests for your service's public API endpoints.
