LambdaTest vs. mabl

As reactnative devs we develop hybrid apps for both ios and Android and testing on different physical devices is very annoying while as with LambdaTest we can just select the virtual device boot that and start testing on the go. No need to keep devices. Sometimes clients report issues and they provide the device name and if available in LambdaTest we can just test and fix the device specific bugs

We haven't found a scenario yet where it hasn't been appropriate. We did have one function on our application that mabl couldn't do, but they solved it and got back to us very quickly. Our application is web-based and mabl is able to handle this very easily. We use the command line runner a lot. Being able to easily and quickly change from a cloud based run to a local run has been fantastic. Setting up flows and environments is a wonderful feature

Incentivized

• Offers geolocation testing in automation which is amazing!
• You can select browsers, timezone, country and run the capability to start testing instantly.
• We could scale up with parallel testing on local environment without any maintenance cost.
• Integration with project management tools like JIRA, CI/CD tools like Jenkins, Gitlab which makes our test cycle easier

• mabl trainer - record and play back test cases
• Organization - labels and flows make this easy
• Customer support!

Incentivized

• More real devices should be added like I have Samsung mobile but it was not in the list
• It takes time in checking the link on LambdaTest if we compare with real mobiles
• Sometimes exact results are not matching as from real mobiles

• Asserts could be easier to add, but they aren't terribly hard

Incentivized

The reason i have given the 10 points becasue the problem LambdaTest solves is providing access to all devices in one place, allowing developers to identify the same errors they would encounter on real devices. This makes life much easier, especially for developers who regularly face cross-device functionality issues. It's a big plus point that positions LambdaTest as an all-in-one solution.

Incentivized

Using LambdaTest feels pretty straightforward once you get the hang of it. The platform has a clean interface so jumping between different features isn’t much work. things feel smooth in UI automation. It takes some time to understand the overall once that is done it'll become easier. The detailed test logs and visual regression features especially stand out in helping you identify issues quickly without extra effort.

Incentivized

yes always available

Incentivized

haven't found any glitch while using this

Incentivized

The customer support team is very active and cooperative. Once, I contacted them in their off timings because of an issue, I got an instant reply from the executive and he resolved the issue very efficiently. This is why we have been using LambdaTest for more than two years. It is best suited for us.

Implementation of Lambdatest was very easy for different project requirements.

Incentivized

While BrowserStack is also a well-established platform, we found LambdaTest to offer similar and even better features at reasonable pricing. LambdaTest is more cost-effective than BrowserStack. LambdaTest provides a free forever plan, while BrowserStack does not. Even manual testing plans are better priced than BrowserStack’s. In terms of UI and onboarding, we found LambdaTest more user-friendly as well.

We ultimately selected mabl cause it most met our needs and our budget. We needed a low code UI automation test tool. We also have a suite of existing testing tools and other tools that it needed to be able to integrate with. Price was the only thing that ruled out some of the above tools, we are a small start up, and don't have a huge budget. Some tools listed didn't have the same functionality or ease of use with the record and playback. mabl works on our machines and integrates with our existing tools

Incentivized

not all department, but we're using for our clients

Incentivized

• Automation testing has a bit of a learning curve
• Lack of real device keep that bug in your head if not on the website.
• Need to wait for a while for a new OS or browser version on the contrary of immediate availability in case of owning a lab

• We are able to more quickly automate UI tests

Incentivized