Adapt Process and Improve Your Codebase to Accelerate Releases in CI/CD

photo-sauce bot mug

Summer is a time of relaxation for many, with folks traveling around the world on summer vacations, firing up the BBQ for neighborhood block parties, or simply spending some time relaxing poolside. However, this time of year can be one of the most stressful for engineering organizations. The holidays are just around the corner, and many companies are gearing up for the high volume of transactions, support inquiries, and website visits that come with it. For these teams, summer time is no picnic!

However, as leadership puts on the pressure to adopt more modern development practices to accelerate release velocity, how many teams are considering testing in this shift? During my five years with Sauce Labs, I have seen many companies undergo massive changes to adopt Continuous Integration or Continuous Delivery (CI/CD), only to experience disappointment when they realize that their legacy testing practices are creating troublesome bottlenecks. Organizations that can optimize their modern development pipelines for continuous testing are positioning themselves for success, as they can deliver on the speed that CI/CD promises while also ensuring they are providing flawless experiences to their users.

Our summer series on optimizing CI/CD for continuous testing is near its end, and has provided a number of tips to help you increase release velocity without compromising quality. It can seem like a tall order, but our technical experts have created a list of the key factors that can help you see the value of automated testing quickly, allowing you to ease barriers to adoption, improve process, and keep your releases green and on schedule!

Our final installment in this series is a second episode of Sauce Labs Tech Talks. Once again I joined Josh Grant, Solutions Architect at Sauce Labs, to discuss how teams can make continuous testing a reality to improve the quality of their apps, increase release velocity, and improve productivity. While our last session focused on environment and feature management, this time we discussed some other key considerations:

Adapting Process: This topic is arguably the most important when discussing how to implement continuous testing best practices. However, for many organizations, it is also the hardest. Everyone has ideas on how to get teams to change processes that are deeply ingrained in a company's culture, but it seems every testing initiative has a graveyard of failed attempts and getting buy-in. For Josh, he was reminded of something a college professor would say, “If you don’t know what to do, do something.” Sometimes the best way to adapt process is to show the value of changing in the first place. By incorporating small changes that make a big impact, it will be easier to affect the kind of cultural change needed to adapt legacy testing processes.

Improving the Codebase: Our other topics in this series have focused on topics that surround the source code of an application. But the fact of the matter is that in order to effectively test code, the code itself must be testable! In this tech talk, Josh shares a few strategies and tools you can use to ensure that your code makes test creation and execution much easier. For example, API libraries can provide a great tool for randomizing user data, allowing your application to stand up to growing test suites.

To dive into these topics, take a look at the tech talk or our most recent technical papers on adapting process and improving your codebase. Making the move to automated continuous testing in CI/CD can seem like a daunting task, but hopefully these and our other resources on optimizing your pipeline give you the inspiration you need to start small and affect real change in your organization. And as the Summer season comes to an end and temperatures start to cool, so does your head knowing that you are releasing better quality features more quickly.

Written by

Alissa Lydon

Topics

CI/CDContinuous testing

Categories