k6 vs. Progress Test Studio

[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

It is very good for testers who have little coding experience but are willing to learn. It is very good for regression testing and really helps us identify issues that could have been a detriment to our end users. It is also great to keep track of the performance of pages across time.

Incentivized

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

Incentivized

• Easy to configure.
• Plugins can be integrated easily with visual studio.
• Takes less time to run all the test scenarios, [and] also generates graphics report for all the tests.
• Keeps bugs [out of] the production.

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

• Client start-up time is a bit slow. Application is a bit sluggish, when there is a lot of tests open.
• Automated scheduling environment is a bit challenging to maintain.

Incentivized

Test Studios had a smaller foot print and allowed us to ease into deploying it in the company. The online help was a great benefit to getting started and the evaluation period allowed us to fully run though the product before purchasing it. Cost difference between the products was a big decision factor as well for the type of deployment we were looking for.

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

• Excellent results, workloads for continuous regresssion testing has been decreased by more than 50 percent.
• Time window needed for regression tests has decreased more than 50 percent.

Incentivized