March 30th, 2021 by Adam Sandman
One of the criticisms of the term DevOps is that on the surface, it doesn’t contain a reference to testing or quality. Continuous Testing is the answer to this criticism, outlining how testing in a DevOps toolchain happens in fact continuously from the Plan stage all the way through to Release and Monitoring. In our new whitepaper, we explain the principles of Continuous Testing and delve into the ideas of Shift-Left and Shift-Right testing that are key parts of the approach.
What is Continuous Testing?
Continuous testing is the process of executing tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate.
- Originally limited to automated tests in the CI portion
- Should include all kinds of testing, throughout the entire CI/CD pipeline
For Continuous testing, the scope of testing extends from validating bottom-up requirements or user stories to assessing the system requirements associated with overarching business goals, and goes all the way to monitoring the system in production to find problems that need to be corrected.
> Read the Whitepaper: Continuous Testing Shift Left Shift Right
What is the DevOps Dance?
As more organizations move towards continuous integration (CI) and continuous delivery (CD) with DevOps pipelines becoming the norm, where is the right place to do different kinds and levels of testing? In this presentation based on the whitepaper, we provide a blueprint for test managers on how to think about shifting left and shifting right while keeping the overall QA picture and goals in mind.