For many, performance testing is a matter of a “final check”: first and foremost companies focus on developing code and only in the weeks before going live do they carry out the necessary performance testing. It is also quite common for companies to only performance test 1 to 2 times a year. While these two scenarios may seem logical, in today’s world they are far from ideal: technological developments, customer expectations, and current internet speeds no longer allow for a less-than-ideal performance. To address the importance of going from yearly to monthly (or even weekly or daily) performance testing, our very own Founder & CEO Amit Patel will be presenting on this topic at the 2019 STP Conference.
Software Test Professionals – Conference Spring 2019
The 2019 STP Conference, which will be taking place this April, is one of the leading conferences on testing leadership, strategy, and management. The most important industry subject areas are addressed at this conference, including performance testing.
On April 3rd, our very own Amit Patel will be presenting on the topic of “Agile Performance Testing in the Real World.” There, Amit will be addressing the consequences of potential performance issues on areas such as quality, cost, and costumer confidence. He will also be elaborating on how his team created processes to execute performance tests on a regular basis and pass/fail builds based on thresholds.
You can find out more details about Amit Patel’s upcoming presentation here. (https://www.stpcon.com/sessions/agile-performance-testing-in-the-real-world/)
Why Is Regular Performance Testing So Important?
1. Performance issues can have major consequences on quality, cost, and costumer confidence
Whilst it may be obvious that performance issues can have an effect on quality and bring about many unexpected costs, another important factor to keep in mind is that it can negatively affect costumer confidence. In today’s world the bars are set high, and costumers tend to have clear expectations that are only met if regular performance testing is taking place. Today, it is necessary to ingrain performance processes throughout the agile development lifecycle. Imagine that, due to a lack of performance testing, you are faced with a terrible crash: you’ll not only have to worry about the costs (both in time and money) of getting everything back up and running, but also the consequences this will have on your image and customer trust in general. An important example of untimely crashes are all of the crashes that take place yearly on Black Friday, resulting in hefty profit losses. According to IHS, North American Businesses’ IT crashes account for an estimated $700 billion in costs, with an accompanying productivity loss of 78% (IHS, 2016). So how can these crashes be prevented?
2. Performance testing allows for the detection of pitfalls before they become an issue (or major crash)
The short answer for how to prevent these crashes is automation. Today’s software is much more sophisticated than anything we’ve ever seen and it’s no longer sufficient to treat performance testing as a final checkbox before we push countless hours of hard work live. To succeed today every organization, regardless of their industry or end user, must design a real-world feedback loop and implement the tools and processes that can analyze data points and turn them into actionable insights. The more these processes are automated, the better! Without this, it is impossible to predict or prevent anything from minor performance issues to major crashes. Performance testing today involves asking the hard questions of why pitfalls weren’t detected at key points along the development lifecycle. It involves discovering the actual cause of deficiencies, and understanding how to resolve a specific shortcoming. It is also important to adjust performance processes so as to prevent any future negative outcomes. Detecting these problems ahead of time with performance testing allows for enough time to resolve them.