{"id":1066,"date":"2016-02-26T10:34:29","date_gmt":"2016-02-26T10:34:29","guid":{"rendered":"http:\/\/www.gallop.net\/blog\/?p=1066"},"modified":"2018-10-05T16:53:03","modified_gmt":"2018-10-05T11:23:03","slug":"integrating-performance-testing-into-app-development-process","status":"publish","type":"post","link":"https:\/\/www.cigniti.com\/blog\/integrating-performance-testing-into-app-development-process\/","title":{"rendered":"Shift Left: Integrating Performance Testing Into the App Development Process"},"content":{"rendered":"

Before we get into the discussion, for the sake of reference and clarity, let us quickly see the well laid out definitions of Shift Left and Performance testing.<\/p>\n

Shift Left<\/strong> is the practice of focusing on quality from day one of a project in order to identify and fix defects as they arise. It requires accountability and increased communication with all stakeholders in the process to ensure the project is staying in-scope.<\/p>\n

Performance Testing<\/strong> is the process of determining the speed or effectiveness of a computer, network, software program or device. This process can involve quantitative tests done in a lab, such as measuring the response time or the number of MIPS (millions of instructions per second) at which a system functions.<\/p>\n

Sometimes even if an organization follows the Agile development practices, it may not be in\u00a0a position to have a ship-worthy product at the end of each sprint. The reason is unresolved issues, which, if found earlier, could have reduced the rework, increased the product efficiency and reduced overall costs.\u00a0This indicates that the team culture lacked in the practice of rigorous performance testing.<\/p>\n

A proper implementation of the Shift Left approach (coupled with rigorous and continuous testing) in such a scenario will help find the problems much earlier \u2013 thereby reducing both efforts and costs, as also increase the quality of the product.<\/p>\n

Per an IBM study, it\u2019s 100 times more expensive to fix a defect found once it has been released.<\/em><\/p>\n

\"\"<\/p>\n

The biggest challenge that most organizations still face is to launch the best quality product with a low go-to-market timeframe at a low cost. This need to deliver better and faster \u2013 continuously \u2013 highlights the need and importance of implementing and practicing the shift-left methodology very religiously.<\/p>\n

What makes practicing Shift Left very important is the fact that it places a lot of due importance on conducting continuous testing throughout the development process, on the need to expand the areas of testing, and thereby on creating better products at reduced costs. With such focussed testing being performed for increasing the effectiveness of a product, the number of defects are bound to get reduced along with the time to go-to-market. This also reduces the complexity of the errors and the time required to fix them \u2013 the major challenges and the nightmare of any Quality Assurance Manager.<\/p>\n

According to a research by Evans Data, only 5% of developers claim to ship apps with 0 defects, while 20% ship with between 11 and 50 bugs.<\/em><\/p>\n

Integration of performance testing into an application development process therefore becomes critical as it helps test every change made to every function. Automated Performance Testing becomes important for testing the more complicated functions as it helps identify \u2013 and thereby fix \u2013 the issues lurking beneath unrelated functions. A recommended strategy is to address these challenges by mandating the tests for every build, which will help verify that the application is working as required and that it is good to hit the market.<\/p>\n

A few things that if defined properly will help integration process a bit more seamless:<\/p>\n