Optimizing CI / CD for Continuous Testing - Feature Management

This technical paper is the second in a series outlining various topics development organizations of all sizes should consider when optimizing their processes for CI/CD, and how they relate specifically to testing.

As more organizations embrace Continuous Integration (CI) and Continuous Delivery (CD) as a mechanism to release apps faster, many find that there are a number of options to consider when making this transformational shift. However, while there is significant thought put into how development practices will change, very few teams consider how CI/CD will change the way they test the code that they create.

This technical paper is the second in a series outlining various topics development organizations of all sizes should consider when optimizing their processes for CI/CD, and how they relate specifically to testing. This critical piece of your engineering strategy can influence not only the quality of your applications, but also how quickly you can deliver them to your users. For many teams, these considerations can effectively make or break their CI/CD initiatives.

Check out even more tips on how to increase release velocity by optimizing for continuous testing by visiting our series on testing in CI/CD best practices.

View white paper

Topics

CI/CDContinuous testingAutomated testing