How Vanguard Got to a CD-CD World by Craig Schwarzwald
1 like201 views
Craig Schwarzwald's document outlines his 12 years of experience at Vanguard, highlighting the transition to a CI/CD environment through automated build pipelines and a new testing mindset focused on microservice APIs. It discusses contract testing with Pact and the implications of dependencies among microservices, emphasizing the need for efficient and reliable builds. Alternatives to Pact, such as Swagger for API documentation and validation, are also explored.
How Vanguard Got to a CD-CD World by Craig Schwarzwald
- 1. How we got to a CI/CD World: A Vanguard Testing Journey Craig Schwarzwald
- 2. About Craig Schwarzwald • Worked at Vanguard for 12 years – Many different roles: • System Tester • UI Developer • Mobile Developer • Automation Engineer • Test Automation Coach – Open Sourced Selenium Framework: • https://github.com/vanguard/selenium-automation-framework.lib • Details available: SauceCon2017: https://www.youtube.com/watch?v=2K2M7s_Ups0
- 7. How did we get there? 2 of our biggest keys to success ❖An Automated Build Pipeline ❖A different mindset in testing Microservice APIs. Contract Testing with PACT
- 8. Investing in a CI Build Pipeline • • • • •
- 9. What is the Microservice API Economy? 3rdPartyService DownStreamJob VendorService ???
- 10. 3rdPartyService DownStreamJob VendorService ??? Traditional Testing - Microservices • • • •
- 11. Traditional Testing - Microservices • • • • 3rdPartyService DownStreamJob VendorService ???
- 12. Traditional Testing - Microservices • • • • • 3rdPartyService DownStreamJob VendorService ???
- 13. Traditional Testing - Sliding Scale Speed vs. Confidence
- 14. Changing Testing Mindset - Microservices • • • •
- 15. What is Contract Testing?
- 16. What if ALL our microservices used PACT? • • Meteorology Service Vendor Service
- 17. What are the down sides with PACT Broker? Your build is now dependent on multiple provider builds. – No way to get End-to-End confidence without executing the providers. • Because these are microservices, builds should be small, fast, and reliably passing (at least on master). Consumers have the ability to break Provider builds. – Can be great to request new features of a provider • But you need to set PACT up to run on tags/branches – (you don’t want to break master builds). – Good luck getting Vendors to implement PACT like this.
- 18. PACT on the sliding scale
- 19. Alternatives to PACT Broker Swagger – Open API spec. – Document how the API works – Endpoints – Response Objects Can be utilized with PACT via: Atlassian’s: swagger-request-validator-pact (JAVA) swagger-mock-validator (JavaScript)
- 20. Meteorology Service Vendor Service PACT Flows Pact Broker vs. Swagger • • Meteorology Service Vendor Service
- 22. Summary • • • •