Abstract
In the last couple of decades, the software development process has evolved drastically, starting from Big Bang to Waterfall to Agile. The primary driver for the evolution of the software was the “Speed of Delivery” of the Software Product which has significantly accelerated from months to less than weeks and days. For IT (Information Technology) Organizations to be successful, they inevitably need a strong technology presence to roll out new software and features as quickly as possible to their customer base. The current user generation tends to use technology to maximum potential and is always striving to keep up with the new trends. The main subject is for the organizations to be ready with their Speed of Delivery strategy adapting to all technology modernization initiatives like CICD (Continuous Integration and Continuous Deployment), Agile, DevOps, and Cloud so that there are negligible customer friction and no risks to their Market shares,. The aim of this paper is to compare the performance testing in every stage of the agile model to the traditional end testing. The results of the corresponding testing phases are presented in this paper.
Highlights
The waterfall model has software development phases accomplished in a sequential linear way which comprises of Requirement Phases, Design, Implementation, Verification and Maintenance
With this study the oncoming demand of Speed of delivery in software development lifecycle is important that performance testing practice must be automated in the pipeline with automated reports that can provide realtime feedback
I think the future of Automating performance testing will be around Shift Left Automation
Summary
Many a times while using a software product or websites during peak holiday seasons and during ongoing high demand promotions, customers come across digital disruptions while using the software products which impacts the end user experience. This issues are caused due to slowness or stability concerns of the applications. Requirements are documented and moving to phase is dependent on the signoff of the prior phase.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Software Engineering & Applications
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
