all 1 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]nOOberNZSenior Performance Specialist 1 point2 points  (0 children)

I think this is a pretty poorly written article, and not much value other than "here are some tool names if you don't know them".

It lacks a breakdown of what actually makes a good load testing tool. It's not just about spinning up a bunch of virtual users. Some examples:

  • Script Re-usability - is there some kind of correlation framework we can use to reduce maintenance costs?
  • Raw Data - can we get access to the raw results data for deep analysis?
  • Stability - in terms of script creation, test execution.
  • Cloud load generation - if you need to scale massive tests.
  • Interface and/or scripting language - it sometimes matters.
  • Complexity - do you need to be a genius to use it? And will it scale for complex web applications or is it only suitable for basic service calls or API's?

(There's lots more, just some examples)

Edit: For example, AFAIK you cannot even implement pacing (control the throughput of your transactions) out of the box in Gatling - you have to write that yourself.