Room
Room F2 - Track 2: Talks
Audience
Architect, Tester, Developer
Key-Learnings
- A test strategy that ensures end-to-end confidence before merging a story.
- Optimizing your development process in a distributed microservices landscape.
- Solutions to challenges encountered while moving to story-based releases.
Do you want to transition from chaos to a streamlined development process? Continuous deployment of small, incremental changes isn't just for tech giants like Google, Netflix, and Spotify; it’s achievable for you too!
This experience report tells my journey of implementing a robust test strategy in the public domain. We started with no development process, a perpetually broken main Git branch, and a mad scramble to fix our environments before going live. In just one year, we transformed this chaos into story-based releases, overcoming practical challenges along the way.
I will discuss the challenges I faced: a system architecture consisting of multiple websites with a distributed microservices landscape, each microservice with its own repository; no testing occurred before merging code to the main branch; and end-to-end testing was time-consuming, typically at the very end of the development process. Learn how we transitioned to a monorepo system, reducing deployment time; created several static dev environments, enabling isolated story testing; and later introduced an even better solution for end-to-end testing before merging code. These steps paved the way to story-based releases.
Join me on this journey, learn how each solution brought new challenges, and discover practical strategies to transform your development process within any domain.
