LambdaTest Reviews

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.

Neutral

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.

At EY, South Africa, my team is tasked with functional testing of any IT solution we are consulting or providing to the clients. As a AQ analyst in functional testing, the majority of my time is devoted to testing the cross-browser compatibility of the website or web app that I am testing. For my cross-browser testing, I am using LambdaTest for automating the testing process, mainly with the help of the parallel testing feature.

It provides 2000+ browser-OS-resolution combinations to work with, which is perfect for our consulting firm, as we don't know what our clients may need. 

We have a Testing lab in our office but with COVID, we were not able to access that. This is why we needed a cloud solution. I was not very confident about having a cloud solution, as they are notorious for being slow and unstable. But, I think LambdaTest is a pleasant surprise. 

It is 60% cheaper and there is no fuss in maintaining the lab, so we have more time to do the testing. The slow nature of a cloud platform was compensated with parallel testing, and now we are able to finish our testing job faster than it was before COVID.

Additionally, is it integrated well with Favor, MS teams, and Jenkins, so it's easier to communicate within the team than it was before.

Mainly, we used it to serve the needs of remote cross browser testing during COVID.

Additionally, it helped to make our deployment faster with parallel testing.

While it is simple to use, LambdaTest is also integrated with our existing tools Jenkins, Microsoft Teams, and Favor.

For responsive testing, they have LT Browsers with a side by side view. It is helpful software for quick fixes around responsiveness.

We are impressed with the stability of the platform and the promptness of the support team. Even during COVID, they were available 24*7.

I feel that the automated screenshot testing takes a little longer on MacOS sometimes.

Though the stability is good, cloud platforms are a bit slower.

The platform provides good emulators and simulators but in the future, there will be a need for testing on real devices. This would be a good addition to future rollouts.

Though the dashboard is clean, there is room for test analytics to get a qualitative glance at results.

Some suggestions on testing will definitely help a newbie working with the platform.

We have been using LambdaTest since April 2020.

We used CrossBrowserTesting but there were stability issues.

We evaluated CrossBrowserTesting and BrowserStack.

Overall, this is a good product. My advice is to talk to the support team before you buy.

The platform is easy to use and has a valuable planning feature. 

I have been using LambdaTest for one month.

I never encountered system breakdown issues. 

The technical support services are excellent. 

Positive

I have worked with different solutions before. I chose LambdaTest because it helps with the planning.

I used the product for free because I subscribed to LinkedIn Premium.

The product supports Java programming needs specifically. I recommend it to others and rate it a ten. 

Partnerize Partner Management Platform (PMP) is an end-to-end, SaaS-based solution for forming, managing, analyzing, and predicting the future results of partner marketing programs using artificial intelligence. It is a real-time technology and, our platform comes up with regular updates and requires it to be tested in all major browsers. This became increasingly important as we built a wide user base across even legacy browsers.

We want our web app to work on every single device, at the peak performance, as any bug or loss of data will result in loss of time contrary to the 'Real Time' promise we give to our clients. So, we have to thoroughly test our whole environment before pushing any changes across all possible use cases.

Before LambdaTest, we were using our own infrastructure of VMs. This was not easy to manage and consuming significant resources on maintenance only. We were a small team when I started working and the DevOps team was already under constant workload, and a VM infrastructure is very costly, especially for us as we need to test our product on multiple devices.

In dire need of scale, we realized our existing practices will not going to last for long. After a lot of brainstorming and product trials, we switched partially first, and then fully to LambdaTest.

LambdaTest was handy and easy enough to save us a lot of time, effort, and money. Especially parallel testing, which was the breather we needed to scale. Without a doubt, LambdaTest is one of the big reasons behind our faster deployment and better team collaboration.

The most valuable feature is reliability. My team automates multiple tests in parallel across hundreds of browsers. The automation grid from LambdaTest is robust enough to execute them without any surprises, every time.

Integrations are very helpful and I have lost the count of integrations that LambdaTest has. The platform is cleverly coupled with all of the other platforms we need on day to day basis for our development needs. Pushing the bug on Slack is a click away, for example. LambdaTest's Slack app gives results of screenshot testing from the Slack command itself. We in fact integrated it with Trello to mark bugs in our tasks and stories. And, we integrated our Jenkins jobs with LambdaTest using its Jenkins Plugin.

Though the platform does well in almost every aspect for us, there are a couple of things they can do to give it an absolute edge.

1. Dashboard Analytics: It would be much easier for us to read the test if they provided dashboard analytics. Though I haven't seen it in this category, I feel this feature can take the platform to another level.
2. Real Devices: LambdaTest has almost all of the emulators and they are good for the most part, but I can see as we grow that we will need real devices. I hope they catch up with that as well.

I have been using LambdaTest for the last year and a half.

We used Virtual Machines prior to LambdaTest. That infrastructure was extremely costly to scale for our ever-increasing variety of browsers. It was also consuming a lot of our DevOps hours.

We evaluated BrowserStack, CrossBrowserTesting, and Sauce Labs.

The primary use case of the LambdaTest platform is to help us scale our testing efforts. We are consistent with our product updates; however, the remote working gave us a backseat in terms of test execution speed.

Our second biggest concern was to attain uniformity and functionality across all of the browsers that our target audiences use. Using LambdaTest, it was easier to scale our testing efforts, plus the team was getting better with writing quality code.

Using LambdaTest, we could run all our functionality tests across various browsers, OS, and resolutions. We have a significantly large user base with some users accessing the product through obsolete browsers like Internet Explorer.

LambdaTest was a big help to test over those rare combinations of browsers and OS. In addition, Lambdatest helped us find UI misalignments and browser compatibility issues faster than before.

A big plus to the automation suite that helped us bring down the time, effort, and cost of our deployment. Thanks to the support team for being available 24*7, and solving rare hiccups, then and there.

The availability of legacy browsers and OS have helped us test rare combinations.

Geolocation testing is as straightforward as ticking checkboxes of browsers, operating systems, and countries. We can ensure that our content is localized and see how it is reflecting on our preferred locations.

The scalability of the testing process helped us deploy faster.

It provides free access to LT Browser to perform responsiveness testing. This is a super intuitive tool for responsivity testing.

Integrations with CI/CD tools like Jenkins and CircleCI discounted a lot of operational load.

LambdaTest needs to have native application testing, which would be a great help to my team. We have requested this feature from the support team but it's yet to be implemented.

We would also like to see more devices for screenshot testing.

We have been using LambdaTest for one year.

We previously used Sauce Labs.

Being an e-commerce website, our main concern was to make sure that we don't lose out on customers due to a bad shopping experience. LambdaTest proved to be a savior for us here, as one platform does the job!

My team was able to test our website across varied browsers, based on our target audience, and reflect on any bugs encountered.

We use TeamCity to manage projects and were surprised to see LambdaTest offering integration with the tool. I would say we stumbled across the right tool at a right time.

Our previous tool was a dent for us in terms of pricing, so while looking out for alternatives, LambdaTest seemed to be the right fit that we could explore.

We had a few doubts about the parallel tests and their pricing, but the support team was efficient and was able to justify and explain the process to set up. Since then, it's been a permanent tool for us!

We needed a robust platform that could help us serve the demand in time. The tool caters to our needs and the one-click bug management is extremely useful for us.

The UI is pretty clean and easy to navigate, and we were able to figure it out very quickly.

The choices of browsers are massive and responsive testing becomes easy.

Integrations and convenience are the win points here.

If possible to simulate the finger pinch, it would make it more realistic.

We had some speed issues while taking the screenshots, for which I got in touch with the support team. I think that this will be looked upon now.

We have been using LambdaTest for seven months.

It is free to start, which means you can actually see how it works and then take the decision to buy.

Using LambdaTest Selenium Grid, we have radically reduced the manual testing effort while ensuring our web application's cross-browser compatibility. It's crucial for us, as a healthcare provider, to make sure that there are no errors.

We had to incorporate a lot of changes due to COVID-19 and our in-house infrastructure plateaued the testing cycles, delaying our go-to-market. That’s where LambdaTest came to pull us through.

LambdaTest is brilliant.

The ease of testing locally hosted URLs over hundreds of browsers & operating systems without worrying about infrastructure issues has led us to deliver better software, faster!

Leveraging LambdaTest cloud infrastructure, we could scale our automation test cycles without much of a struggle. Our automation team could execute Selenium scripts in their preferred language, and the ability to test parallelly helped us optimize our continuous deployment.

Thanks to LambdaTest, we can find more critical bugs with less manual testing efforts.

LambdaTest offers geolocation testing in automation, which is amazing! You can select browsers, timezone, and country, then run the capability to start testing instantly.

We could scale up with parallel testing in local environments without any maintenance cost.

Support documentations are of good help to run tests parallelly.

Also, it offers integration with project management tools like JIRA, CI/CD tools like Jenkins, and Gitlab, which makes our cycle easier.                                             

Mobile application testing will be an added benefit for us if LambdaTest implements this really soon.

I would also like to test on real devices, and we have communicated the same to their support team.

I have been working with LambdaTest for one year.

The support team is highly responsive, so they will guide you better.

We previously used Sauce Labs, and we switched for better pricing.

The setup is super easy.

LambdaTest is priced well, which is why we migrated to it.

When we began with LambdaTest almost a year ago, we were thinking of implementing shift left testing to catch bugs ASAP. With browser testing being one of the most rigorous and time-consuming validations, we were looking for a solution that could help us achieve continuous testing through our GitLab CI/CD pipeline. That is when we landed over a webinar of LambdaTest, which demonstrated setting up GitLab CI/CD and integrating it with their cloud. We thought of giving the integration a try and it worked like a charm.

We were able to leverage the Git-based triggers to execute our CI/CD pipeline. So, every time a new commit was pushed from our end, the pipeline ran an automated build over the LambdaTest Grid, which allowed us to ensure our UI on every major and minor release with access to numerous browsers, platforms, and devices.

Integrating LambdaTest in our GitLab CI/CD pipeline allowed us to deploy quality builds faster. In the new normal, where companies are forced to perform remote testing due to COVID-19, a cloud-based solution like LambdaTest has been a life-saver. It gives us the flexibility to run tests from anywhere at any time without being bothered about maintaining an in-house infrastructure.

LambdaTest Grid integrates with a variety of CI/CD tools. It provides a variety of browsers, OS, devices, all on the cloud.

Consistent with browser updates when new versions are released, they even provide beta versions of browsers.

Our test execution time was reduced to 16 mins from five hours when executed in parallel on multiple VMs. This has been extremely helpful!

Their smart testing module needs improvement.

We also hope they could come up with some API for automated visual regression testing.

One more thing is that it would be good to see if Lambdatest can get real devices to test for mobile automation.

I think these features and improvements will be a robust fix to the product.

We have been using LambdaTest for almost one year.

It is affordable as compared to similar SaaS solutions.