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, I will 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.
Firstly, I will outline how you can improve the testing being done during development in CI by adding early testing for functionality, usability, performance, security, and accessibility (shift left).
Then, I will outline how you can improve the ‘testing’ (actually monitoring and feedback) being done after CD in production so that issues that were missed prior to deployment are caught and remediated early (shift right).
Finally, I will cover the important ‘middle’ part of testing that is after the development pipeline is done and before the code is deployed into production. Even with DevOps and shift-left/right approaches, there is a critical phase where you need to assess the technical risk before making the decision to put code into production.
Wrapping it up will be a blueprint for test managers containing the different levels of testing that should be done in each of the three stages, and how the insights from each phase informs the next one.
- How you can shift left by adding more testing to your DevOps Pipeline.
- Ways to shift right by adding monitoring and tracing for applications in production.
- Putting it all together into an integrated end to end test management process.
- Some tools both open source and commercial that can help along the way.
Adam Sandman | Director of Technology | Inflectra Corporation
Adam Sandman was a programmer from the age of 10 and has been working in the IT industry for the past 20 years in areas such as architecture, agile development, testing, and project management. Currently, Adam is a Director of Technology at Inflectra Corporation.