PractiTest vs. TestMu AI

For most of the test case scenarios, PractiTest works fine. If we talk about one specific feature then it would be the automation side. I like this feature a lot just because it made all testing so easy and effortless but on the other hand automation in this platform comes with so many limitations and that's where I am not fully satisfied.

Incentivized

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

• Effective Test case template.
• Can integrate with different Atlassian products.
• Report generation.

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

• Better dashboard display capability (drag and drop to rearrange gadgets)
• Creation of global user groups (as opposed to just project groups)

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

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 chat button is available to anyone who logs into PractiTest. In my experience, the support has always been very quick, very friendly, and very thorough. They make sure that your question is answered in a way that you understand it. They also provide documentation of best practices so you are never left hanging on what to do next.

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

I've used many different Test Case Repository tools, and while each of them has its perks, I like the capabilities of PractiTest best. When creating a test in qTest for example, you can only input information into the fields provided, and you have everything set up in a folder tree structure. With PractiTest, we are able to create custom fields and filter our tests based on those fields to provide more accurate information in a readily available format while quickly searching for the filter instead of through a folder tree. TestRail did not appear to meet our needs as a company. It just didn't have the potential that we found with PractiTest. Zephyr for example worked seamlessly with Jira, which is really nice since that is what we use for the most part. However since we cater to many different clients, we needed an external Test Case repository so we could use something that wasn't tied to 1 Jira instance.

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.

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

Incentivized

• Test Reporting
• Defect Management

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