Consumer-Driven Contract testing in Cookpad

A slide for the ICST meetup event: https://www.meetup.com/Tokyo-Software-Test-Quality-Meetup/events/238376025/

Transcript

1. Consumer-Driven Contract testing in Cookpad Introduction of our software development and Pact as a Consumer-Driven Contract testing tool 5BJLJ
   0OP
   !UBJLJ
2. This talk • Introduction of our software development ‣ What we do - our products ‣ Team organization and system architecture ‣ Building and releasing • Consumer-Driven Contract testing ‣ Problem and our approach ‣ What is Consumer-Driven Contract testing ‣ How it works in our environment ‣ Lessons we learned
3. Who is this speaker? • Taiki Ono (@taiki45 on the Internet) • Cookpad member since Mar. 2014 • Working in Developer Productivity team ‣ Goal: Keep developer’s productivity at high level ‣ Develop tools, build deployment system, design architecture and more..
4. Introduction of our software development
5. What we do • Solving problems around cooking ‣ To make everyday cooking fun ‣ Recipe sharing service ‣ Cooking school service ‣ and more..
6. Products • Cookpad for sharing recipes in Japan • Cooking School • Video for cooking videos • News about cooking • and more..
7. Product scale of Cookpad • over 63 million monthly active users in Japan *1 • 20,000+ test cases (It’s not related to product though) 
   $PVOUT
   FWFSZ
   BDDFTT
   GSPN
   POF
   PG
   UIF
   EFWJDFT
   PS
   CSPXTFST
   BCPWF
8. How our team are organized Cookpad team Cooking School team Media team … SRE DevInfra
9. Our system architecture Cookpad app Cooking School app Video app … Auth Notification News app Payment …
10. Teams and systems boundary Cookpad team Cooking School team Media team … DevInfra Cookpad app Cooking School app Video app … Auth Notification News app Payment …
11. Building and releasing Github Enterprise Rundeck Test job Build job +FOLJOT Dev servers Prod servers $BOBSZ
    %FQMPZ "84
    &$4
    PS
    &$
12. Building and releasing Github Enterprise Rundeck Test job Build job +FOLJOT Prod servers 1SPE
    %FQMPZ Slack "84
    &$4
    PS
    &$
13. Consumer-Driven Contract testing in Cookpad
14. Problem • Our architecture has been shifted from Monolithic to Microservices • Testing integration points became hard ‣ We tested them by usual test suites (in- process) before, but now components are separated ‣ Running real components are expensive and too fragile and slow
15. Our approach • Simple stubbing ‣ Stub all HTTP requests using WebMock or VCR ‣ Problem: Can’t detect breaking changes of API
16. rack-vcr • github.com/miyagawa/rack-vcr ‣ Capture HTTP req/res in server-side request (feature) tests. Then use them to replay server behavior in client-side tests.
17. How rack-vcr works
18. How rack-vcr works 'BJM $PNNJU
    CSFBLJOH
    DIBOHFT
19. Problem with rack-vcr 5IJT
    EPFTO`U
    TDBMF
20. Consumer-Driven Contract testing
21. Consumer-Driven Contracts (CDC) • “.. which imbues providers with insight into their consumer obligations, and focuses service evolution around the delivery of the key business functionality demanded by consumers.” • https://martinfowler.com/articles/ consumerDrivenContracts.html
22. Consumer-Driven Contracts
23. Consumer-Driven Contract testing
24. Pact • CDC testing tool • For Ruby, Java (JVM), Swift… • Also mentioned in “Building Microservices” book
25. How it works
26. How it works
27. Pact in Cookpad
28. Pact in Cookpad • github.com/taiki45/pact_junit_formatter
29. Good parts • We can detect breaking changes in CI ‣ Already detected breaking changes some times • We can do Test-Driven Development even in separated components development
30. Bad parts • We have to write too many tests ‣ Most of them are enough with type checking ‣ Since Ruby has dynamic type system, that type checking might be run in tests
31. Future works • Introduce type schema ‣ Write type definitions of API and check them in compile time or tests ‣ Use CDC tests in important or complicated integration points • Context naming problem ‣ It’s difficult to name “context” to keep consistency and uniqueness in entire name spaces