The software industry is changing at a very rapid pace and the time to market has become more critical than ever before. The waterfall model was one of the most prominent software models that were used by organizations, but it had a major drawback – testing was not done at every stage of software development, due to which highly critical bugs were left unnoticed until the software reached the production stage. Such a scenario could also lead to business losses, like buggy software being shipped to the end-customer, a problem that is present in every traditional develop-first-then-test models. This gave rise to more evolving models like Shift-Left testing and Continuous Delivery testing where testing is considered an integral part of the development function.
What Is Shift-Left Testing?
In a traditional development model, testing is performed only at the end of the development cycle in the Requirement gathering (Planning), Analysis, Design, Development, Testing, and Deployment phases. There is a cost associated with testing, identifying, and categorizing issues, and pushing the development changes into the product. The costs might rise if the test/verification team comes across an issue of very high severity (release blocker issue) at the end of the lifecycle. Such issues could even stall the entire release.
from DZone.com Feed http://bit.ly/2G5AaaB
No comments:
Post a Comment