I have a team that is not heavy on programming skills. I am looking for a load testing tool that is easy to use. Preferably, the tool should be a record and playback tool without much programming. Also, the tool should be able to test APIs apart from web-based applications. What tool should I opt for?
My choice would be Apache JMeter, It's free and opensource plus it comes with lots of plugins and extendability. Apache JMeter needs a small amount of a learning curve and a basic understanding of Network, Protocols (TCP/IP ports, HTTP(S) and REST/SOAP, etc.) for initial setup. But it doesn't require programming skills. it has a nice record and playback option. You can still carry on without the developer skillset if you follow these steps. 1. Take backup. 2. Start recording and interact with the application. 3. stop recording and save the test case. This will give you your test-bed, after this, after these steps, every time just do Restore from backup and then Playback and observer results.
If you have longer recordings then an understanding of how to modify the recorded scripts will come handy.
For some of the advanced features such as Configuring variables, implementing loops, throttling adding think time, and automating test scaling to the number of users will require good planning of test scenarios and a Developer experience but this is true for any tool (even loader.io)
Disclaimer: I work at k6, and I recommend you try our tool.
It might require some coding skills, but we support a few options to record a user session to autogenerate the load test. Read How to record a browser session with k6 OSS.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Gatling?
What is Loader.io?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
This is the best open source tool i have ever come across which does load testing at its best.
Python config code is really simple to write and good part is its extendable and there are many hooks available ... what else you need ..
Lastly, the web UI to monitor your swarming activity is too good and very helpful for identify bottlenecks and spikes real-time.
I don’t remember exactly how I heard about Loader.io. I think I was adding load testing services to Leanstack. I saw it was a SendGrid Labs project, so there would be competent people behind it. And since they had a Heroku Add-On it was easy to get started. Loader.io is cool because it’s super simple to set up.
When executing tests, you can see error rate and average response times. But we also check the Heroku logs to see if they are real errors.
My biggest complaint: figuring out what load to set for your tests is difficult. We don’t understand the language they use and no one we’ve spoken to that has used Loader.io understands it either. We’ve been testing at 250 clients (maintain client load) for all of our tests on 2 dynos. That means a constant load of 250 people using the site over a minute, or so I thought. The number of requests at the end of the test suggests it’s more like 250 additional clients hitting the site every second for a minute. But I guess accommodating a higher load is better anyways? 250 concurrent users seems to be our average HN traffic spike so that’s why we went with that load.
I use loader.io for distributed load testing.
That especially matters when you have a cross-region load-balancer and you want to make sure how your app behaves on a global scale.