Consumer Driven Contract Testing with Pact and Docker. By Harry

Transcription

1 Consumer Driven Contract Testing with Pact and Docker By Harry 1

2 2 OR CONFIDENCE IN PRODUCTION

3 In the beginning, there were monoliths Image from: 3

4 And then came Microservices Image from: 4

5 Which meant loads more communication Image from: 5

6 Example Service Authentication Service Invoice Service Backend for frontend 6

7 Example API 7

8 And so chaos ensued Image from: 8

9 The problem with testing Test all the services together in one go Need a rig to host all of your services at once Local testing is very difficult Providing services need to be spun up locally Internal integration tests Not proof the services will actually work in the real world Image from: 9

10 10 Consumer Driven Contracts

11 What are Consumer Driven Contracts (CDCs)? A contract between a consuming service and a providing service, stating what the consumer wants from a providing service, in a defined format 11

12 Benefits of Consumer Driven Contracts Enable services to be deployed independently Enables teams to work independently from each other Enables verification of external endpoints am I building what is wanted? 12

13 What they aren t A test of business logic An SLA between services A way of validating / verifying external services 13

14 Back to the API 14

15 15 How Rightmove use CDCs

16 CDC check list A consistent format to describe Request/Responses An easy way to create Consumer Driven Contracts A way of storing these Contracts An easy way to test CDCs in our CD pipeline An easy way to run tests locally 16

17 A consistent format Loads of languages available: - Java - C# - Go - Python - Ruby - PHP - JavaScript - Plus more 17

18 Rightmove s CI and CD pipeline Images from: 18

19 Rightmove s Artifacts Images from:

20 Fitting CDC s into the pipeline 20

21 Running the Pact Tests for a provider 21

22 Example: UK-Location 1. Download latest Property Web/Property Management pacts for UK-Location 2. Download the stubbed UK-Location 3. Start the UK-Location 4. Gradle runner reads the Pacts, and sends requests and checks the response 5. Shut down the UK-Location 6. Publish the results 22

23 Consumer tests 23

24 Example Property Web 1. Download latest Pacts for a Property-Web, for UK-Location and Property-Search providers 2. For each provider a. Download stub b. Gradle runner reads the Pact between the Property Web and provider, and sends requests / checks response c. Shut down provider 3. Publish results 24

25 CDC check list A consistent format to describe request responses An easy way to create Consumer Driven Contracts An easy way to add these tests to our CI/CD pipelines A way of storing these contracts An easy way to run tests locally 25

26 Testing Locally Faster to spin up and use Way less custom code / logic Easier to run different project types not just java Platform-agnostic Images from: docker.com 26

27 Provider Tests Images from: docker.com 27

28 Consumer Tests Images from: docker.com 28

29 Are we there yet? A consistent format to describe request responses An easy way to create Consumer Driven Contracts An easy way to add these tests to our CI/CD pipelines A way of storing these contracts An easy way to run tests locally 29

30 The Future Parallel Tests Greater insights into our services, using Pacts Easier Pact version upgrading Open sourcing what we ve done 30

31 Questions? Feed back and We re also hiring. Come speak to me after! Or me: Or head here: References Consumer Driven Contracts: A Service Evolution Pattern The Pact Foundation: Pact JVM library: Docker: 31