06. Why do performance testing initiatives fail
TRACK 2
Why do performance testing initiatives fail?
Rohit Singh, Scale and Performance Engineer, Network and Security Business Group at VMware
While this may sound negative, the best way to avoid failures is by contemplating the possible ones when planning and executing your project. Unfortunately, scale and performance testing has many such pitfalls and it is easy to fall into one.
Here is a few of them:
Testing a lot but not covering the real-world scenarios
Quest for too many tests that require too much maintenance but uncover no problems. Unlike functional testing, the number of tests might actually be inversely proportional to the value they bring
Half-automation requires you to wait an hour and then download a report that makes you a night owl waiting for a load test to finish
Test that only runs once when automated, no continuous execution? What!! You have a magic wand and you only use it once!?
Test results that can not be repeated because the environment changed!? You don’t have the environment anymore? Ever heard of Infrastructure as Code?
Not able to use a baseline from the last release? For running one test you actually have to run two?
All your tests are benchmarks?