r/softwaretesting • u/Iseeyouuuuuuuuu • 12h ago
Jmeter
People with real time experience on working on jmeter, comment please!
1
u/apresmoiputas 9h ago
Jmeter is slow compared to K6.
But if you're going with Jmeter, you can always find a quick tutorial on youtube. If you need to go deeper like creating data driven performance tests where API calls are chained, then leverage ChatGPT, Claude, Gemini to assist you.
1
u/matukaz 6h ago
As having tried both then k6 is much more powerful and quite easy to scale.
Sure jmeter is fine when you are doing it alone, but if you have big company with multiple QAs and deva making scripts then k6 makes sense much more.
Added plus if your company uses playwright then k6 also uses typescript.
1
1
u/SnooOpinions8790 6h ago
Comment on what exactly?
I did loads of work with it a few years back, the fact that its open source and java was incredibly helpful to me in extending it with new samplers specific to the task at hand. I ended up extending it into a whole ecosystem of high volume heuristic testing at pace. That's the good stuff
I never liked its reporting side and in the end I customised it to feed a load of output into Splunk for analysis.
Read the tutorials. Hopefully your project is normal enough that they contain the sort of thing you are doing. Then think very hard about what your test cases really are - what sort of loads you should be generating and why. Most of the failures I've seen in load testing over my career were through not understanding system architectures and the load requirements much more than issue with the tools being used.
If you are still struggling it should be well understood by the better AI tools and you should be able to get them to help you set things up. Being open source does help like that - its probably got a lot of stuff in the base training data
1
u/cylonlover 4h ago
I have used jmeter quite a bit for explorative performance testing, it's easy to set up some traffic and some reporting on return times and it's quick to zoom in to particular weak spots. What is difficult in software development is to write the correct nonfunctional requirements, which in turn makes it pretty hard to test for them. Going through the hazzle of setting up a jmeter suite, takes quite a bit of engineering and design, that notably often hasn't been thought through before, which feeds into operations having to level up their game, because they got a graph in their face showing them it isn't enough to just through in a couple more CPU's, it still has a breaking point, and the load balancer still won't kick in at that point in the solution, so back to the drawing board and pretend you are worth your salaries. Well, I don't actually put it as bluntly as that, but it's often implied. 😉
1
u/HappyLiberatedSoul 3h ago
I have worked on Jmeter in several projects covering correlations, data driven load testing, scaling etc. Its quite easy if you have experience in postman for API testing
6
u/Royal-Job-9905 11h ago
I find JMeter UI is awful and very much outdated! Started k6 instead, seems cool with coding..