Apache JMeter is old
"JMeter is old technology", I hear this a lot.
"Let’s use this tool or that tool instead of JMeter as it’s the latest", I hear this a lot.
"We need a lightweight tool without the GUI interface to write our tests as that will make us more agile", I hear this a lot.
It’s all nonsense it really is, there seems to always be a call for using the most modern technology for all forms of testing whether its Performance Testing or Automated Functional Testing and the result of this is that the people writing the tests spend to long learning the new tools and not enough time building something that will ensure the software being developed is the best it can be.
I am conscious that the above statement is a bit or a generalisation and there are some exceptions but for many organisations this is true.
The aim of all these tools is the same thing, to support your QA journey through to the delivery of a robust, well performing piece of software, the tools you use to accomplish this are not important if you have a robust modular framework in place, and you have a sensible approach to data management and reporting.
We are going to look at in this post the reason why JMeter is so good at what it does and why just because it is considered old technology by some still makes it the right choice for many testing professionals.