As the information economy rapidly matures within a software and services delivery model, the cost of unplanned downtime can take a significant toll on profits, productivity, and revenue. These risks lie largely in how software testing is traditionally done. A new approach is needed to streamline software testing, which can ultimately reduce downtime, increase productivity and protect organizations from certain bugs and errors.
The Danger in DevOps
The DevOps model has dramatically changed how testing and development cycles work. To remain competitive, software developers must continually release new application features. They’re sometimes pushing out code updates as fast as they are writing them. This is a significant change from how software and dev teams traditionally operated. It used to be that teams could test for months, but these sped-up development cycles require testing in days or even hours. This shortened timeframe means that bugs and problems are sometimes pushed through without the testing required, potentially leading to network downtime. Adding to these challenges, a variety of third-party components must be maintained in a way that balances two opposing forces: changes to a software component may introduce unexplained changes in the behavior of a network service, but failing to update components regularly can expose the software to flaws that could impact security or availability.
from DZone.com Feed http://bit.ly/2N70m9W
No comments:
Post a Comment