Mobot vs K6

Mobot is amazing! Great partner to make sure we don’t have any surprises when we release new versions of our SDK! This has been a huge game changer for our mobile team and has saved us and our customers a ton of time and headache.

- Lewis Chung Engineering Manager at Persona

Can’t say enough about how much better I feel with each release now that Mobot is part of the pipeline. Our stability rating for iOS is now at 100%!!!

- Swamy R CTO/COO of Sandboxx

For companies with native mobile apps, Mobot uses mechanical robots to automate mobile app tests that were previously impossible, eliminating error-prone, tedious manual testing and ensuring higher quality, bug-free app releases. Mobot uses real, mechanical robots to automate physical testing, a proprietary 4th test driver technology, on over 200 mobile devices. (Check out their homepage to see their testing robot in action.) Supervised by humans, the robots automate business-critical test scenarios, capture results, and integrate into your release process. Their robots test like a human. They tap. They swipe. They toggle between two phones, between apps, and third-party devices. All Mobot customers are assigned a Customer Success Manager who verifies robot test results. You get the best of both worlds: efficiency and speed of automation, with the judgment and verification of manual testing.

- Jason Boog

"Developer-Friendly Performance Testing Tool & Infrastructure" What do you like best about k6? -Excellent documentation and supportive blogs (and video content like the Office Hours series) content simplifies getting started with k6 -Developer-friendly -- Easy to install and get going in the CLI. Makes performance testing more accessible to not just a few, but all of those on an engineering team. This is so important as performance testing is no longer just an expectation of a single niche quality team because of limitations of licensing or knowledge of an antiquated tool. -k6 cloud -- So far, ensuring the ability to scale our tests beyond the resource of our machines has been reassuring. The analyses and comparison features between test executions is helpful so far. Looking forward to the continued work against this infrastructure platform. Review collected by and hosted on G2.com. What do you dislike about k6? -The user experience of using k6 with npm modules is not consistent with what you expect from typical development -xk6 extensions conceptually are great as a community is helping to build out a need. Just be cautious of utilization as they may not be supported long-term, though these extensions are featured in k6 documentation. Review collected by and hosted on G2.com. What problems is k6 solving and how is that benefiting you? k6 has made performance testing an accessible practice for engineering teams. It's a rather low barrier to entry (getting started with k6) , yet you can get as advanced as you with, customizing your scripts as you need to get the insights required. Because of this tool, I'm seeing engineering teams starting to take on the responsibility of knowing and testing the limitations of their APIs and tiers.

- Lindsay H.

"K6-Game changer for API Load and Performance test" What do you like best about k6? It is developer friendly and easy to write load tests and has excellent documentation. Most importantly it is a straightforward K6 report that can tell where the performance issues are. We did a thorough analysis where we compared several tools/frameworks and we can tell with full confidence that K6 is much superior compared to other tools. These are some of the benefits: It is easy to install and start writing the first L&P test, code review It is great community support and excellent documentation Excellent Report and Integrates with NewRelic, CloudWatch if we decide to retire later it is easy to do because we can still run locally without being locked to one tool. I would call the K6 a modern L&P framework that can beneficial for any company. Review collected by and hosted on G2.com. What do you dislike about k6? I wish it had better support for HTTP protocols. It is awesome with API test but not so great with UI load test. Review collected by and hosted on G2.com. What problems is k6 solving and how is that benefiting you? Ensuring that API we develop performance well at Production. It is not a guessing game anymore. It is a data-driven decision.

- Talgatbek K.

What do you like best about k6? It's ease of use, readability and its fantastic set of constantly evolving features, paired with a vibrant community - which together with its good performance makes, to me, the best option for performance testing. And its extensibility as well... Tests are code, as they should. And readable code! Review collected by and hosted on G2.com. What do you dislike about k6? There is an extensibility /plug-in system but some integrations are still not covered… To complain about something, its only issue is that apart from the excellent readability of the tests, they still need to be written, so you need to know what you are doing- thank god- I still have a job. But give it time… (summary: tests needs to be written, haha) And the fact that you have to write in JavaScript - it would be fantastic to write in your own language such as C# as in my case :) Review collected by and hosted on G2.com. Recommendations to others considering k6: Check other options, make your own decisions. My criteria might not match yours. My decision points were the performance vs. features, mainly its code readability, how easy it is to define a real test, its open model, and extensibility. Review collected by and hosted on G2.com. What problems is k6 solving and how is that benefiting you? excellent, readable performance tests that evolve with the application, as code. One test source code fits all, so its simplicity is key.

- Jose Luis L.