Test Leadership Congress 2020

The recent revolution in software development,  including agile / interactive development, cloud computing, continuous integration, and many more, opened new opportunities for performance testing and affected its role in performance engineering. For example, early and continuous performance testing is becoming the new norm. However, performance testing in general and specific performance testing techniques should be considered in full context:  including environments, products, teams, issues, goals, budgets, timeframes, risks, etc. The question is not what technique is better, the question is what technique (or what combination of techniques) to use in particular case (or, in more traditional wording, what should be performance testing strategy).

Drastic changes in the industry in recent years significantly expanded the performance testing horizon: agile development and cloud computing probably the most. Basically, instead on single way of doing performance testing (and all other were considered rather exotic), we have a full spectrum of different tests which can be done at different moments; so deciding what and when to test became a very non-trivial task heavily depending on the context. We need to create and run different tests mitigating different performance risks.

So the art of performance engineering is to find out the best strategy of combining different performance tests and other approaches to mitigate performance risks to optimize risk mitigation / costs ratio for, of course, the specific context.

This session will provide you the insights of understanding various types of performance risks, which  test techniques and practices to use in a specific context to measure and evaluate system performance, and how to interpret the data derived from these tests in order to drive performance engineering excellence.