DevOps.com
Where the world meets DevOps
Using Incident Response for Continuous Testing 2 Comments Incident response tools offer the ability for organizations to not only implement continuous testing but to also shorten the feedback loop from continuous testing back into planning and development Recent Posts By Chris Riley What Is Resilience Engineering? Moving from NOC to the SRE Model The Difference Between Capacity and Scalability Planning More from Chris Riley Related Posts Using Incident Response for Continuous Testing BlazeMeter Launches Mainframe Continuous Testing: Mainframe Testers Can Now Shift Left 7 Strategies for Continuous Delivery and Deployment Success Related Categories Blogs Continuous Testing Related Topics continuous integration functional testing performance testing vulnerability scanning Show moreShow less At this point, you should be able to say the word “continuous” to any technical team, drop the mic and leave. Yes, the idea that we want to do more delivery, more testing and more interactions isn’t always novel. The reason we use phrases such as continuous testing and continuous improvement is to have the conversation about the unique set of tools and practices required to run these processes in production, and not just as part of continuous integration (CI). Part of supporting continuous testing is having a highly effective incident response process—arguably, it’s required.Continuous testing is faster and more effectively. This is the other continuous, continuous improvement. Continuous Testing Tagged With: vulnerability scanningClick to share on Reddit (Opens in new window)MoreLike this:Like Loading... Sponsored ContentFeatured eBook TechStrong TV: strongDM With Betterment »
2 Comments
Incident response tools offer the ability for organizations to not only implement continuous testing but to also shorten the feedback loop from continuous testing back into planning and development
At this point, you should be able to say the word “continuous” to any technical team, drop the mic and leave. Yes, the idea that we want to do more delivery, more testing and more interactions isn’t always novel. The reason we use phrases such as continuous testing and continuous improvement is to have the conversation about the unique set of tools and practices required to run these processes in production, and not just as part of continuous integration (CI). Part of supporting continuous testing is having a highly effective incident response process—arguably, it’s required.
Continuous testing is faster and more effectively. This is the other continuous, continuous improvement.