Source: devops.com
Using Incident Response for Continuous TestingCategory: Database
Home » Blogs » Continuous Testing » Using Incident Response for Continuous Testing
At this point, you should be able to say the word “continuous” to any technical team, drop the mic and leave.
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).
Continuous testing is used in the context of functional testing, performance testing and vulnerability scanning.
In particular for vulnerability scanning, continuous testing allows SecOps folks to get alerted when a new vulnerability is detected, which can result in patching holes long before the application is exploited.
At this point, you should be able to say the word “continuous” to any technical team, drop the mic and leave.
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).
Continuous testing is used in the context of functional testing, performance testing and vulnerability scanning.
In particular for vulnerability scanning, continuous testing allows SecOps folks to get alerted when a new vulnerability is detected, which can result in patching holes long before the application is exploited.
Related Articles
Community Partners
DevOps Careers