When we start doing performance testing, there are mistakes almost all of us make that can ruin the results. Today I share 5 mistakes that ruin your tests (and that almost all of us make at the beginning).
5 mistakes when starting with performance testing
- Always using the same data. You are not simulating 500 users, you are simulating the same person logging in 500 times.
- Not adding assertions.
- Launching all users at once. That's not how people arrive at a system: the load has to be realistic.
- Ignoring think time. Real users read, hesitate and get distracted. That has to be simulated too.
- Running the tests with the graphical interface open.
Watch the video to find more information about it. And tell me: when you were starting out, did you make any of these or other mistakes?
And don't forget to join the JMeter course.
Frequently asked questions
What are the most common mistakes when starting with performance testing?
Always using the same data, not adding assertions, launching all users at once, ignoring think time and running the tests with the graphical interface open.
Why shouldn't you always use the same data?
Because you are not simulating 500 users: you are simulating the same person logging in 500 times.
Keep reading: Performance testing with JMeter and Most frequent errors when starting in testing. If you want to go deeper, I recommend the course Performance testing with JMeter.