1.
CONSUMER DRIVEN CONTRACT
TESTING WITH PACT
The evolution of your APIs supporting with
tests
@nelisboucke @matteo_pierro

2.
Overview
● Why?
● What is Contract Testing?
● Code example with Pact
● Challenges

3.
Overview
● Why?
● What is Contract Testing?
● Code example with Pact
● Challenges

4.
A STORY…

5.
A STORY…

6.
NOT COVERED BY TESTS?
Trustworthy
Cheap TargetedReliable

7.
Integration tests
Use running
system
Use mocks
Reliability - +
Speed - +
Targeted - +
Environment setup - not needed
Test data - +
Easy to automate - +
Trustworthy + -

8.
IF ONLY WE COULD VERIFY THE MOBILE
TEAM'S MOCKS ……..

9.
Overview
● Why?
● What is Contract Testing?
● Code example with Pact
● Challenges

10.
Contract Testing flow →

11.
Overview
● Why?
● What is Contract Testing?
● Code example with Pact
● Challenges

12.
E-commerce →

13.
Code Example →

14.
Overview
● Why?
● What is Contract Testing?
● Code example with Pact
● Challenges

15.
Challenge: collaboration?
PACT does not solve your collaboration problems
● Provider must verify consumers’ expectations
● Consumer must check expectations with the provider

16.
Challenge: Rework?
PACT replaces your previous mocks
● Rework / Extend consumer tests to for this

17.
Challenge: When Applicability?
● You want to integrate fast
○ Evolving application
○ Fast feedback
○ Reduce integration risk
● Limited and known consumers
○ Typical settings
■ Single organisation, multiple teams
■ Frontend backend
■ Microservices

18.
@matteo_pierro@nelisboucke
Questions?