Sunday, 30 October 2016

- Why is Continuous Testing recommended for DevOps



 
The word DevOps had been formed by combining the development and operations functions. It is not a technology, rather an IT culture. It emphasizes ways in which development, operations and testing can collaborate more effectively. DevOps can be defined by four key activities:
-      Collaborative Development
-      Continuous Integration and Continuous Testing
-      Continuous Release and Deployment
-      Continuous Monitoring
DevOps, to some extent, reduces the need for testing and testing resources. However, this does not imply that DevOps does not require testing. What really happens in  DevOps Testing is that it brings testing into the mainstream of development process and avoids the problems created by having the testing left to the end of the cycle which causes release delays and quality issues.
Before code integration, the developers need to test their code. One of the most integral parts of the DevOps process is the regular release or the continuous deployment of the working software. The only way to support this rapid cadence of releases is through automated testing. Faster release cycles put a significant pressure on manual testing. This problem can be resolved through automated testing of the critical aspects. 

No comments:

Post a Comment