UiPath vs LambdaTest: Which is a better fit?

Alexander C.: Hello, my name is Alexander. I am an RPA developer. I give UiPath a four out of five and for more videos like this, please click below. We use UiPath at my company and team to translate data from an [inaudible 00:00:16] systems to the client's system. Normally this would be a manual process. However, using UiPath, we are able to translate from our forms to the client's forms. That would normally be done through an online portal, the robot then inputs all the data that we've retrieved either through an SQL database query or through our own Google document forms and put phones through it into the client's Systems. UiPath is excellent for those who are not solely technically minded. A lot of the processes that we fulfill with UiPath have to come through a business analysts mind and where business analysts are seeing a waste of time. So in theory, robotic, and it'd be hard for them to delegate that, to a technical person. Whereas with UiPath, they can simply create that process themselves, as it's all very low code, very user friendly, and the workflows are quite easy to read. So someone with a business analyst background and point of view can fill that need very quickly and efficiently. I dislike some things about this UiPath. For example, there are still some issues regarding crashing and other bugs that have not been ironed out. For example, if you undo certain things within certain scopes, it will appear like nothing's happening, but you'll come to realize that it's undone something from another scope and you have to go back in searching for that also it does not remember from project to project, what variables you've been most recently using. So you have to go through a very slow interface to go grab specific variables from other packages.

Speaker 1: I'm Karthik. I work as an engineering manager. My rating for LambdaTest is three stars out of five. For more reviews like this, please click the link below. BrowserStack was the other platform that we evaluated before we tested out LambdaTest. And in our experience we felt BrowserStack was a little bit more mature as compared to LambdaTest. [inaudible 00:00:34] a little bit more pricier, but we found BrowserStack to be a little bit more mature given that they were in the industry longer than LambdaTest. Our first choice was BrowserStack, but cost was definitely a barrier, which is why we decided to evaluate LambdaTest. I believe it was fairly easy to onboard this platform, but I think it can still get challenging depending on how bespoke your particular environment is. You may run into specific challenges integrating this tool into your platform depending on what sort of custom implementation you have on your end. So that's something to keep in mind. If it's a fairly vanilla implementation, shouldn't be too much of a problem. It should be quick and easy. But if you have like a custom implementation, then there could be challenges integrating this into your platform. You definitely have to take into consideration the environment that you have and if LambdaTest will work from the standpoint of being able to want support all of the browsers and the platforms that you're looking to run your tests on. The ease of writing and maintaining tests that comes with something like LambdaTest, the barrier to entry in terms of learning curve for your engineers with respect to picking this platform up and being able to run with it. And then last but not the least, cost is also a factor. So that's something to keep in mind as well when you evaluate a platform such as LambdaTest.