The document discusses the integration testing of services in a consumer-provider architecture, emphasizing the use of mocks and stubs for simulating external dependencies. It highlights the development of contracts using Spring Cloud Contract to define API behavior and enable independent work among multiple teams such as the front-end and API teams. The goal is to automate verification and maintain synchronization between the components of the webshop checkout project.

1. 1

2. •
•
•
•
•
• 2

3. 3
●
●

4. 4
Checkout Service - Consumer Order Candidate Service - Provider

5. We know the individual modules work
5

6. All the modules in the system work together
6

7. Check the integration with an mock of the external dependency
7

8. • Mock is a method/object that simulates the behavior of a real method/object in controlled ways.
• Stubs are programs that simulate the behaviors of software components (or modules) that a
module undergoing tests depends on.
8

9. 9

10. 10

11. 11

12. 12

13. 13

14. Test the service in the real integrated environment
14

15. 15

16. 16

17. 17

18. 18

19. 19

20. 20

21. 21

22. Participants:
22

23. 23
Checkout Service - Consumer Order Candidate Service - Provider

24. 24

25. 25

26. 26

27. 27

28. 28

29. 29

30. Developing Contracts with Spring Cloud Contract
30

31. • Replacing the existing WSP Checkout
• Starting with multiple teams
• Front-end team (WSP Checkout)
• API team (Checkout API)
• Needed
• Some way to define API behaviour without API being available (Mocks)
• Being able to work independently without getting ‘out-of-sync’
• Solution
• Formalize using Contract defintions and automate verification
Webshop Checkout Project
31

32. 32

34. 34

35. 35

36. 36

37. 37
visualisation of the contracts
dependencies between all known
consumers and producers

38. 38

39. till next bol.com
Stephan Oudmaijer