On Test Reviews

No. 1 mistake I see junior performance testers making is the premature test development conclusion.

That’s the test scripts that are pushed for large scale execution as soon the test script compiles and returns a “success” in the first iteration.

Here’s a few questions to ask yourself before you push a unit test disguised as a performance script:

– How will this workload scale?
– If I run max No of users, should I expect race conditions?
– Is the parametrization sufficient?
– Am I using and freeing the resources the same way the customers will? (connections, transactions, correlation)
– Is there a chance my script will become a bottleneck?
– What if the same user runs a few iterations?

The most problematic parts for new testers are usually resource handling (especially for non-recorded scripts), inter-thread communication handling, runtime test data handling and poor assertions.

“working” performance test is usually never enough

Follow me for more performance memes
And share if you found it useful