The Test SDK: The SDET's Best Friend in Monolith-to-Microservices Migrations
Transitioning from a legacy monolith to a distributed systems architecture presents both opportunities and challenges for the test automation engineer. It's exciting to use new modern test frameworks that are not bound by the confines of the legacy stack but daunting at the same time given its possible for your test architecture to go "wild west" quickly. How does one unify and standardize automation test architecture as more and more new services are spun up?
In this talk, Wayne outlines uShip's approach to overcoming the hurdles involved moving to distributed systems, how we developed an internal test software development kit to facilitate writing test automation and the lessons of how things have worked using the test SDK a few years later in our distributed system journey. He'll demonstrate how the SDK created an extensible strategy that enabled centralized methods of test data creation, standardized core test helpers, and allowed for simple distribution and updates for the engineering teams. We'll also show how creating the SDK allowed us to easily roll out new future projects and improvements to our test automation in the ever changing evolution of our software.
- What are some of the challenges of writing automation in a distributed system
- What is a test SDK and what all can go into it to help your teams
- Why it's important to standardize test automation architecture (when possible)
Wayne Ng
Wayne Ng is currently a Principal SDET at uShip and has a decade of experience in the testing space, ranging from building test automation suites, to establishing accessibility, chaos testing and monitoring practices.
Outside of work, Wayne enjoys exploring nature, photography, eating good food and spending time with his wife and kids.