Pact is a contract testing tool that enables consumer-driven contract testing, allowing teams to test integrations without deploying the full stack.
Field note
Pact is a contract testing tool that enables consumer-driven contract testing, allowing teams to test integrations without deploying the full stack.
Capabilities
Tags
Ways to use it
JavaScript / @pact-foundation/pact
Not filed / https://docs.pact.io/implementation_guides/overview
Not filed / https://docs.pact.io/implementation_guides/overview
Not filed / https://docs.pact.io/implementation_guides/overview
Product features
Pact allows consumers to define expected interactions, driving provider features.
Guidance on writing consumer tests, including best practices and rules.
Write unit tests for your client class to verify request creation and response handling.
Share the generated pact files with the provider team.
Supports HTTP-based interactions.
Tests each interaction independently using a mock provider.
pact-jvm project for Java microservices.
Use matchers to reduce test fragility.
Supports message-based interactions for queues.
A compatible Pact implementation in all commonly used languages.
Pact can generate contracts for non-HTTP communications, like message queues.
Pact is open source and welcomes contributions.
Generates pact files after consumer tests pass.
Formats v2, v3, v4 support multiple provider states, messaging, and generators.
Allows setting up provider state before verification.
Use provider states for clarity and maintainability.
Run provider tests to verify that the provider meets the contract.
Original implementation in Ruby, used as a standalone executable.
New reference implementation in Rust, wrapped by client languages via FFI.
Pact verifies that provider responses match the expected contract.