BlazeMeter vs. k6

It is well suited for applications that are mission-critical or applications that can receive high traffic/transactions at unscheduled time periods. Using the load testing feature of BlazeMeter, we can test and ascertain the capacity of the application without the drawbacks of the usual Apache JMeter load testing which depends heavily on the host system from where the load testing is performed.

Incentivized

[k6 (formerly Load Impact)] is well suited to run performance automated suites and to run stress tests, spike tests and load tests[.] We can run tests from recorded [sessions] but we cannot run npm modules and we cannot run nod js libs[.]

Incentivized

• Results are easy to read
• Tests can be run easily
• Tests can ben imported easily from jMeter

Incentivized

• Load testing
• Stress testing
• Performance testing
• Spike testing

Incentivized

• BlazeMeter should not require the purchase of 2 dedicated IPs for each suite of performance tests.
• BlazeMeter should make custom packages cheaper than they are today when purchased for an enterprise and should include dedicated IPs in the package.
• BlazeMerer should have integration with Jenkins Pipeline 2.0.

Incentivized

• I would like to see k6 run in browsers
• I would like to be able to import npm modules
• I would like to see k6 has a GUI

Incentivized

Personally, I prefer using JMeter + Redline13, however we had some business folks that wanted to be able to run a few of their own tests. The non-technical individuals preferred to use Blazemeter because of its simple and intuitive UI.

Incentivized

• It helped positively by helping to identify the maximum capacity needed for high traffic periods
• Saved revenue by eliminating unwanted duplication of systems

Incentivized

• K6 make its easy to engage Devs in testing
• Extremely fast installation make it count for us
• Not using all system resources is a great benefit

Incentivized