This document discusses consumer-driven contract testing and introduces Pact, a testing framework that uses consumer-driven contracts. It poses four problems around evolving services without breaking clients. It then describes the basic flow of consumer-driven contracts where the consumer generates and shares a contract with the provider to test against. Pact enables evaluating contracts throughout a provider's development cycle to ensure fast, confident and less error-prone continuous delivery of services.

1. CONSUMER-DRIVEN
Contract Testing
PRAVITHA NAIR/SUNITA VENKATACHALAM
TARGET, BANGALORE

2. PROBLEM
STATEMENTS
1. How can something be added to a
service without breaking the clients?
2. How can something be removed
from a service without breaking the
clients?
3. How can a service developer find out
how clients are using their service?
4. How to enable short release cycles
and continuous delivery of services?

3. Provider

4. Consumer

5. BasicFlowof a
Consumer
DrivenContract
CONSUMER
generates a Consumer
Driven Contract
PROVIDER works with
CONSUMER who re-
generates contract and code
PROVIDER changes code
that results in change in
contract ; contract breaks
CONSUMER shares
the generated contract
with the PROVIDER
PROVIDER includes
the Contract
Verification as part of
their unit test

6. PACT.io
Pact.io is a testing
framework that
evaluates CONSUMER
Contracts are satisfied
all through
development cycle of a
PROVIDER

7. PACT- DEMO

8. WhyPACT?
 Confidence
 Continuously evolve your codebase
knowing that Pact will guarantee
Contracts are met.
 Faster
 No need to wait for integration testing in
end-to-end environments. No need for
manual testing.
 Less Error Prone
 Generation and verification of Contracts
are automatically managed by Pact.

9. Questions?