Releasing to production 5 times a week without automated tests? It is possible, and might even be beneficial. Setting up test automation capabilities are a long road to travel, but should that stop you from releasing frequently while building those capabilities?
I work at a place that does daily continuous delivery. We have very little test automation. We weren’t always like this. Several years ago we used to deploy once a month. This session is about our journey, how we got there, and what we’re looking to still improve on. It’s purpose is to share my story, and give hope and ideas for others on their journey.
- Why and how delivering continuously improved our quality even without automation.
- How continuous delivery changed the way we do exploratory testing with developer-tester collaboration.
- How we use Git branches to control the delivery contents and schedules for split value without effort estimates.
- How we’ve organized for gradual improvement towards higher degrees of automation that we need in the long run.
Maaret Pyhäjärvi is a tester extraordinaire specializing in breaking illusions about software through means of exploratory testing. She is a software specialist with soft spots for hands-on testing, helping teams grow and building successful products and businesses. She’s been working with software since 1995 in various roles and delivers talks as popular speaker in Finland as well as internationally. She works as a tester at Granlund and trains testing on the side through Altom.