We are doing manual testing, covering the overall scope. There are multiple dimensions that need to be tested. And regarding the trouble, like, there were some information issues on certain devices, and that's why we needed to check those on the same devices.
The solution is very handy. And the device support is very good. I like that the technical support team handles it all in one, too.
There is room for improvement in support. The community should extend support. Like, Lambda has a huge community, and support should be available online.
Another area of improvement is stability and performance of the solution.
I have experience with the solution.
The solution is stable, but I've noticed some issues with the speed and overall performance. For example, when I'm using my development laptop, and I switch to LambdaTest, the performance decreases. This is especially noticeable when I'm using a dimension that is working on the laptop, and I try to use the browser. In general, the availability of the device could be improved.
Other than that, I've also had some issues with the speed of certain API calls and the rendering of data. For example, when I'm onboarding data, the process can be slow.
My main concern is that the camera is not available when I'm using LambdaTest. However, I've been able to work around this issue by using the camera to check my connections.
Overall, I would rate the stability a seven out of ten.
It is a scalable solution. We are three end users, and we are planning to extend the usage.
There is room for improvement in customer service and support. It's a solution that was implemented years ago, and not a huge community really good. So that's why maybe we can work on technical support.
It was easy to set up. It was not hard. You just need credentials and set up the virtual devices, and that's good to go. I am looking forward to integrate it with Slack and Jira.
It's pretty good to use and to write the code for the manual automation and even for the developers to debug this thing. It's a pretty wholesome solution. That's why we prefer to get the solution. Because not only the testers can look into this, but the development team can also use the tool.
Overall, I would rate the solution a seven out of ten.