Common
Mistakes in Performance Testing
I believe that before the real execution,
preparation or planning test is very important. After we put performance plan in place, we start scripting.
Just take
a break and let’s discuss about some of common mistakes or missed pointers
during performance testing.
·
Ignoring
the performance test plan during design
·
Direct
jump to multi-user tests
·
Test
results not validated
·
Unknown
workload details
·
Too
small run duration
·
Lacking
long duration sustainability test
·
Confusion
on definition of concurrent users
·
Data not
populated sufficiently
·
Significant
difference between test and production environment
·
Network
bandwidth not simulated
·
Underestimating
performance testing schedules
·
Inappropriate
base-lining of configurations
·
Inadequate
User Think Time in Scripts/Not Including Think Time
·
Using
Hard Coded Data in Every Request
·
Ignoring
System or Script Errors Because Response Times and Throughput Look Okay
·
Run
Tests from One Location
·
Over-technical
on Results Reporting
·
Performance
testing is performance tester’s job
·
No
assertion in the script
·
Not
Documenting
·
Looking
only for server crashes
·
Overloading
the load generators
·
Focus on
one single or too many use cases
These are
points which may lead us to inaccurate results or not getting useful results
even performing good job on coding part. Performance testing is team works. Involving
all person from each section of Software architecture is very important.
We can
discuss more on this topic. Please feel free to provide your inputs on
comments.
Happy testing!!!
Comments
Post a Comment