As a member of the Sauce Labs team, I am lucky to work with our customers as they enter on their continuous testing journeys. Teams of all sizes have undergone massive shifts in their ontogeny practices, mainly through the rise of Uninterrupted Integration (CI) and Continuous Delivery (CD) as ways to deliver characteristic more speedily to their users. However, they quickly realize that in order to achieve the velocity that CI/CD is capable of, they also have to modify the way they test those lineament. And while most tally that testing recitation demand to change, where I find teams have the most enquiry is, “ where do we begin? ”

Our ongoing summertime series concentre on CI/CD with continuous testing, and we have lashings of tips to help you increase your freeing velocity without compromising quality. Optimizing your line for automated testing best practices can seem like a toughened labor, but considering a few key factors can help ease barriers to adoption, improve summons, and ultimately keep your users happy with innovative, bug-free features released at the speed that they demand.

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

In our most recent installment of, I join Josh Grant, Solutions Architect at Sauce Labs to discourse how surroundings and feature management can aid teams of all sizes embrace continuous quiz to proceed quality codification moving through the pipeline more quickly. We discussed two particular areas where squad can see important effect:

Environment Management: Teams who want to attain red hot speeds in CI/CD know that they can entirely go as tight as their environment will allow them to, and the same applies for testing. It ’ s important for teams that are building out uninterrupted essay drill to consider the environment they involve for testing throughout the pipeline. And the good word is that there are a bit of pick available for test environments throughout the pipeline. From headless browsers for factor tests providing fast feedback to developer, to full mark browser regression tests later in the development lifecycle, applying the appropriate environment at the right stage in your grapevine can help improve productivity, decrease cost, and most significantly increase release velocity. Furthermore, team that borrow a sound environment management scheme for testing see an increase in borrowing across distributed teams.

Feature Management: In order to loose more features more apace to your users, you have to change the way you build that application. Breaking up massive application into smaller feature branches is a very common recitation, but it ’ s significant to see how that vary your testing scheme as well. In fact, feature arm can aid you embrace more testing throughout your CI/CD grapevine. Smaller features signify more they are more testable, and allow for tryout automated best practices to flourish. One of my favorite citation from Josh around this is “ You can do test mechanisation without CI/CD, but you can ’ t do effective CI/CD without full test automation. ” This means write tests at every stage (functional, unit, API) that are. Furthermore, smaller features mean it ’ s easier to turn them on and off, and it allow for mechanics such as lineament masthead or canary freeing to effectively test lineament without compromise user experience.

To learn more about these topics in optimise CI/CD for continuous testing, insure out our on surround and lineament direction. These two considerations can help your team take your CI/CD to the next stage, and assist you achieve blaze fast speeds in CI/CD.