LambdaTest Reviews

For testing and automation. We do cross browser testing for different versions of subproducts.

We don't use it for mobile app testing. We are planning on using it in the future for that. 

The real devices feature.

Load flow compared to other stacks needs improvement. 

I have been using LambdaTest for one year. 

Twenty five users are using at the moment. The scalability is an eight out of ten. 

The initial setup is straightforward. 

The pricing could be made cheaper. 

Overall, I rate the solution an eight out of 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.

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.

Running tests serially can be a good option when your product is at an early stage. However, as we scaled the product, we needed a tool to reduce test time execution and pace up our test cycles.

LambdaTest simplified the Selenium testing experience for us with their cloud-based platform, which allowed us to execute our test cases in parallel on hundreds of browsers. We could easily automate the test cases, get the sessions recorded, and share the test reports across the team for the assessment using Asana integration.

We even leverage the integration with CircleCI to run automated tests on LambdaTest through our pipeline. The CircleCI Orb is handy for testing our privately-hosted application.

It’s good to see, now that we are using LambdaTest, we can run multiple tests on multiple VMs, saving us hours of testing time and the maintenance cost of local infrastructure. 

Personally, one thing I find that LambdaTest does very well is continuing to provide tutorials for testing, so that we stay up to speed and are even able to learn new things. I definitely saw myself applying a lot of the new concepts that I learned from their blogs.

LambdaTest easily integrates with leading project management, bug tracking, and CI-CD tools like Jira, Asana, Jenkins, Circle CI, and more.

As we use Asana, it was good to see that LambdaTest provides support to the tool, as it made our task much easier.

The support documentation is precise and could actually help you get started, without the need for the support team.

We can test on local environments faster with CircleCI Orb with an extensive range of browsers and devices to test on.

Responsive testing UI is a bit cluttered, whereas the LT browser is much better to use. We had a few slugs in the early stage of implementation while running parallel tests; however, the support team was helpful in resolving it.

I have been using LambdaTest for seven months.

We evaluated Sauce Labs and we chose LambdaTest because it was an affordable product with a good feature set. 

This is an affordable product.

LambdaTest has helped me gain more customers. I was not aware of how cross-browser compatibility could make a huge difference for my website. Now I have both devices compatible and a responsive website. All thanks to LambdaTest.

I got attracted towards LambdaTest services by reading a review on a website. It made me think — is it really important for my business? Now I am a happy customer of LambdaTest. Their customer support is just amazing, and all my queries relating to the tool gets resolved in a jiffy.

We are continuously using LambdaTest to check every development we do. It is browser compatible and working flawlessly on all browsers.

The unbelievably neat and intuitive user-interface gives me clarity for all my test logs and even helps me save my test so that I do not have to choose them again. 

I did face some minor issues, but after talking with their customer support, they took it as a priority and got it resolved. So I am happy and want to see more features they could add in future.

It's stable, and its performance is good. 

Good.

If you are opting to use LambdaTest, you are in the right direction. You will find much more similar solutions like LambdaTest, but you will not find exactly LambdaTest in other platforms.

Yes, I did use BrowserStack for few months, but it was too costly, and also we are not happy with its kind of performance, so we are looking for an alternative.

It's very straightforward.

In-house.

Superb.

I think it is the cheapest platform in today's market. 

No, after that, we gave a first try to LambdaTest as it seemed quite good, and after giving it a try, we stuck to it. 

Yes, they are doing a great job.

The most valuable features are that it's essentially on-demand, and you only focus on getting the code that needs to be executed without having to worry about the OS, hardware, etc.

It would be useful if LambdaTest had a library of code that first-time developers could copy and paste. In the next release, Lambda should add integration with Cucumber.

I used LambdaTest for three to four months.

If the code is done properly, then LambdaTest rarely requires maintenance.

The scalability is good with Amazon, but IBM had some issues.

LambdaTest's technical support comes in different tiers - most issues get resolved, but there's room for improvement with critical issues.

The initial setup is straightforward.

LambdaTest is paid per execution.

It's useful to learn some best practices for Lambda - if you have thousands of instances in an IoT ecosystem, you need a framework and governance to keep track of where the code is and what's what. I would rate LambdaTest as nine out of ten.

When the pandemic demanded us to work from home, it was a daunting situation for us. Keeping up with the consistent growth for the past year, we had a few feature-launches ready to be deployed on production environments. However, testing them was a challenge while working remotely and with a large team of testers and developers.

We wanted a tool where the team can work collaboratively at a faster pace and get started with deployments.

LambdaTest is a saving soldier for our company by offering us thousands of browsers & platforms to test on the cloud. We are able to ensure a sturdy UI without worrying about infrastructure management.

It receives plus points for a Docker extension, where we could locally test on multiple instances through the Lambda Tunnel using Docker. This helped us align better with our DevOps team, it kept our projects on track and allowed us to implement continuous deployment with robust quality checks.

The Docker tunnel integration for local testing can be extremely useful to run on multiple instances in parallel.

The fact that it integrates well with tools like Jira and Slack makes team collaboration even easier.

Also, it is worthwhile to mention that the support team is actively listening to your feedback and issues. As we wanted to get our product tested on the latest Safari 14 browser, our request was considered and they updated to the browser within two weeks.

Analytics could be better because as of now, it gives basic information on test status and build status. It would be better if I could analyze groups of tests that are taking a long time to complete, to pin-point use cases which could lead to slowness in the user journey.

It would be nice to have an API for visual regression testing.

We have been using LambdaTest for six months.

Using LambdaTest automation has allowed us to run all of our functionality tests suits across multiple browsers and OS.

It has helped us identify UI misalignment specific to browsers or functionality failure due to incompatibility with a particular browser.

The good part is that you can automate screenshots and get insights into where and which browser your website’s UI is going off. Then, we can use the live feature to identify and debug the compatibility issue.

We strongly believe customer experience is the key and that could impede your product growth. With LambdaTest, we could see improvements in identifying errors before our customer does.

This product offers out-of-the-box geolocation testing in automation, which is amazing!

You can select browsers, OS, country, and start testing instantly.

Further, it offers integration with CI/CD tools like Jenkins and GitLab, which makes our cycle easier.                                                                            

For us, Cypress! It looks like the support for Cypress is not there. The tech support guys say it would be there in a few months, but let's see.

Mobile application testing would be helpful for us. We have been asking the support team for this feature but it's yet to be implemented.

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

There is a latency in a single test when compared to a local machine. Maybe because of the cloud? So, you have to run in parallel to cut down on testing times.

We have been using LambdaTest for eight months.

As said, we perform multiple tests for browser coverage, so we have scaled up our testing pipeline and are now running multiple tests in parallel. This scaling up was way too easy. No more adding VMs for testing locally.

The implementation was done by our in-house team. However, the support team from LambdaTest was very helpful to begin the process.