UiPath Test Cloud Reviews

I have multiple use cases. We build automation across platforms of UiPath, including Test Suite. It helps with document understanding and Citrix automation. UiPath automates regular tasks. I had to build an automation to extract information from a web interface and upload all the information to all the data to a terminal interface.

In Test Suite, I work with Oracle and SAP. It provides integrations to both.

We have an in-house Oracle testing team, and they've been tasked with HCM and ERP solutions on Oracle and have completely cloud-based interfaces. The Test Suite has helped us to build testing specifically for quarterly upgrades. We were able to integrate a significant workload during the quarterly updates. 

The complete test automation framework is quite useful. It's helpful for testing end frameworks and for building test cases.

I've explored usage across a couple of applications and it's been great. I've not had any issues, especially in the web-based sector. 

Within two months, we were able to realize the benefits of Test Suite since we had to do extensive testing. The automation helped reduce the manual labor usually needed for quarterly testing. 

By itself, it provides a lot of integrations with more than a thousand applications. We could use it for Oracle and SAP and it did help significantly.

While I don't have exact numbers, the time to value was good. 

The solution can cost more than other options.

I've used the solution for more than six years now. 

The solution is definitely scalable. The only challenge would be that if there is a significant requirement change, it would need additional development and deployment.

Technical support from UiPath is very helpful. 

Positive

We also use Power Automate for automation; we did not use a different solution for testing. 

The initial deployment was straightforward. The suite deployment does not take much time. However, it takes time building other test cases and the initial unit testing and user acceptance testing. Deployment, I would say, took approximately one week. We built out about 60 use cases. 

There were three of us that handled the deployment - one junior developer, one senior developer and a solution architect. We did a cloud-based implementation. It was deployed on Azure using virtual machines. 

There's only maintenance if there are process changes for particular implementations. 

We did not use any third-party vendors as part of the deployment process.

The ROI was impressive. For example, for one client, we developed a solution that helped reduce effort by three-fifths. We were able to reduce the equivalent of three full-time employees for every upgrade. 

Automation Anywhere technically offers much better pricing and it's relatively more transparent than UiPath. However, UiPath is more customized for specific client requirements. They also provide a wide variety of features for the price. 

There may be extra costs, depending on the requirements. If it's a standard automation, there are no additional fees.

We did a market evaluation and found this solution to be the best option. We looked at, for example, Automation Anywhere. AA does not provide as many integrations. Also, UiPath architecture is superior and has a better interface to manage automation compared to Automation Anywhere. 

We are UiPath partners. 

While it depends on the scenario, for those who think automation testing is too complex, I'd say the framework provides a good automation opportunity. You can even do complex testing as long as there is good repetition.

I'd rate the solution eight out of ten. 

We use UiPath Test Suite to test the workflows designed in UiPath Studio.

UiPath Test Suite helps to automate our web applications and desktop applications. It is easy to automate tests from a wide range of technologies.

UiPath Test Suite helps to test the automation of the application that we have created. We can check whether we are getting the expected results.

Previously, we used to do manual testing by running the processes one by one and making a note of each test case. By using UiPath Test Suite, we have a test framework. In that framework, we can use some conditions. Based on the conditions, we can check whether the workflow is executed successfully or not. The UiPath Orchestrator also has a feature to get a screenshot of the error message.

UiPath Test Suite has definitely saved costs and time. I do not have the metrics, but in general, manual testing of a normal process would take us about 5 days, and with UiPath Test Suite, we can complete the same in three days.

Being able to use regular expressions, activities, and attributes is valuable. 

The integration of UiPath Test Suite with other UiPath products is easy.

We have output arguments in the workflow. We are able to check results only by using those arguments. It would be better to have some more options, such as screen variables. For example, in a workflow, if we want to check if an activity is present inside, we should be able to get the output to UiPath Test Suite through the activity itself. That would be great for testing.

I have been working with UiPath Test Suite for 3 years.

It is very stable. I would rate it an 8 out of 10 for stability.

Sometimes the server might not be accessible during peak hours. There might be a lag, and the unattended bots would not run. It could give us a failure status. This issue is related to server maintenance from our side. We then talk to our IT team to increase the bandwidth on the server.

I would rate it a 6 out of 10 for scalability. They provide updates once a year or twice a year. In those updates, some of the activities that we have already developed might go missing. Their developers should concentrate on the older versions of the activities that they are developing.

Their support is great. I would rate them a solid 9 out of 10. We generally get a response on the same day for the ticket. We sometimes schedule a call with the UiPath team so that we can show them the issue because we cannot share confidential information through emails.

Positive

We were not using any similar solution previously. We were testing manually. We were running the workflow in the same way as an attended bot.

It is deployed on a private cloud. Its initial setup is straightforward. We just need to connect it from the UiPath Orchestrator to UiPath Studio, which is on Windows. It takes 30 to 40 seconds. It is just a connector.

It does not require any maintenance from our side.

I deployed it myself.

I am not aware of the exact cost. It seems reasonable, but it is an additional cost. 

We did not evaluate other options.

Overall, I am satisfied with UiPath Test Suite. Anyone can learn how to use it. There are a few tutorials on the UiPath Academy. By using those tutorials, anyone can easily use UiPath Test Suite.

I would rate UiPath Test Suite a 7 out of 10.

We use the UiPath Test Suite to perform regression testing on the third-party vendor systems that we rely on. When a new update is received from the vendor or we make any configuration changes, the regression tests we created with UiPath Test Suite help identify any potential issues.

Automating our regression testing with Test Suite saves our QA Analysts many hours of testing whenever we receive vendor updates, or we make configuration changes. We receive vendor updates monthly and quarterly. QA analysts no longer need to perform end-to-end regression tests and can concentrate their manual testing efforts on testing the new functionality.

Our automated regression tests have found problems with new vendor releases almost immediately, while manual testing might have taken a couple of weeks to find the same issues. We are finding the issues faster so we can open tickets with the vendor, who can then fix them and send us a new release. Under manual testing, it could be a couple of weeks before we would find the bug, and then we would have to open a ticket, wait for the vendor to fix it, and then deploy the fix, which could delay the release to production. This way, as soon as the bug is found, we open a ticket with the vendor and then simply run the test again when they provide a new version.

The best thing about Test Suite and UiPath in general is that they are easy enough for business users to use. Our QA analysts, who are not technical, have been trained to use Test Suite to automate regression testing because the tool is easy enough for them to use. UiPath has excellent training resources, including free training resources on its website. As a result, we are no longer paying expensive developers to create the regression tests. Instead, the QA analysts can automate regression testing themselves.  

UiPath's tools are generally designed for business users, so they can be as simple or as complex as needed. Although the UiPath Task Capture tool is not part of the Test Suite, we use it to gather the steps that need to be performed for regression testing, so we have a clear picture of what needs to be done. Task Capture has been a great help for automated regression testing.

UiPath’s Test Suite manual testing doesn’t work for our organization based on how the QA Analysts do their manual testing and the artifacts that are needed for deployment. The QA Manager needs to track which tests have been completed, the success rate, and other relevant information. The ability to have manual tests show up in multiple projects is a requirement that is not easily done in Test Suite.

We have submitted the following enhancements request to UiPath and are waiting for them to address these issues before migrating our manual testing to the UiPath Test Suite platform.

• Ability to import manual test cases from an Excel Spreadsheet.

• Ability to create release folders and have manual tests under the folders (sub-folders are also needed).

• Ability to copy tests between projects (manual and automated).

• Ability to execute manual test cases in any order and skip tests if needed.

• Ability to assign and see who has been assigned to test cases – need to know who created the test case and who executed the test case as they could be different people.

• Ability for the QA manager to see which test cases have been run and which haven’t as well as which ones were successful, and which weren’t.

• Ability for the QA manager to track defect cycles for a particular release.

• Improving Search functionality – must enter the exact test case name in current search functionality.

• Ability to extract key data for artifacts for Release Management or Audit

  • Test Set or Individual Cases,

  • Include Test Results (passed / failed),

  • Include how many iterations a test case went through until it passed.

I have been using the UiPath Test Suite for three years.

UiPath’s technical support has been exceptional. They respond to my tickets in a timely manner, typically within 24 hours. If the problem is related to a lack of knowledge or training, they will provide knowledge-based articles to help me solve my problem. If the problem is more complex, they will ask for additional information or schedule a call to troubleshoot the issue.

Positive

We were using Ranorex Studio which required developers to both create and run the tests. This meant that whenever regression testing needed to be done, the QA team had to reach out to the developers. This was not very efficient. From a testing perspective, our QA analysts are the ones who are most familiar with the platforms we use. They understand how the platforms should work and what issues might arise. Therefore, when we switched to UiPath, we implemented a model where the QA analysts were responsible for creating and running the regression tests. This way, the QA analysts can automate tests and run them as needed. UiPath Test Suite enables us to use this model, so we do not need any formally trained developers to do automated testing for third-party vendors.

The initial setup of UiPath Test Suite was straightforward. All of UiPath's products are easy to set up. Once we paid for the license, it was activated in our version.  We configured Test Manager for the tenants we wanted to do regression testing in. There was a learning curve in that we had to learn how to use Test Manager, but overall, it was very simple and was done by one person.

The implementation was completed in-house.

I am not a fan of the UiPath licensing model which is used by the major vendors in the RPA space. I prefer a consumption-based model because it provides greater flexibility for trying new products offered by UiPath and allows us to only pay for the time an automation is running (process automation or automated tests).  Under the licensing model, I must purchase licenses upfront to handle the volume and need to purchase extra licenses to handle peaks in volume. These extra licenses are used to handle peaks, so the utilization of these licenses is low which makes them expensive to use.

UiPath Test Suite is a powerful tool for automated testing by non-technical QA analysts. However, its weaknesses in manual testing may make it unsuitable for having all testing (automated and manual) within one tool. We have adopted UiPath Test Suite for automated testing but continue to use Azure DevOps for manual testing. For teams that don’t have strict requirements for manual testing, UiPath Test Suite may be sufficient.  Our QA team finds the features lacking in UiPath Test Suite, but our Process Automation Team uses Test Suite for the manual testing of our automations.

It can be difficult to justify automated regression testing using traditional Cost Benefit Analysis (time and $ saved manually compared to automated) but in our case, finding issues with vendor releases earlier justifies the effort for creating automated regression tests. We are using Automation Hub to capture regression testing requests and compare the costs of manually running tests multiple times per month compared to automating the tests. Automation Hub provides a nice graphic showing the benefits which are supplemented with the intangible benefits of finding issues earlier.

UiPath Task Capture is a valuable tool for regression testing as it can provide the basis for the automated test. The tool allows you to generate a document with step-by-step instructions including screenshots as well as an XAML with a blueprint for the automation. I highly recommend using Task Capture for starting your regression tests.

Finally, I would recommend that you create a dashboard that indicates how many times regression testing found issues and report that to senior leadership to show the value that automated regression testing brings to the organization.

We use Test Suite for many types of testing, including origination, smoke, and web application testing. We are slowly migrating all of our test cases, but so far, we have primarily used it for our smoke and regression test cases. We mostly automate Windows .NET technologies. UiPath also works with web application frameworks like React, Angler, and Java. 

UiPath Test Suite helps us automate our testing. Other tools like Selenium require you to learn the language, or you need a specialist to write the scripts. With UiPath, we can automate manual testing using team members who are not that technical. It's easy to learn and requires no coding skills. So we were easily able to achieve our objectives.

Web applications are always easy to automate. The challenge is implementing or automating a Windows application, but we can do that successfully. UiPath Test Suite has freed staff to work on other projects. It's hard to quantify, but the initial time savings was high because it runs 24/7. One manual tester works 40 hours weekly, and we had four testers, so that's 160 hours. We can now complete the same work with around four hours of manual work. 

It's easy to integrate UiPath with other tools like Azure DevOps for running those bars and generating the test history. It also comes with out-of-the-box Jira integration. Hundreds of tools are available, and it integrates with most of the popular ones. Some tools, like Micro Focus Octane, don't have native integration, but UiPath has connectors for those.

UiPath has also reduced the time spent on maintenance. Otherwise, when we make changes, we need to test all the steps manually. We're progressing toward becoming fully automated, but it has cut maintenance time in half so far. 

Test Suite has multiple tools that are fully integrated. It has everything you need to record your test cases, generate your documentation, and integrate synthetic data with your Orchestrator. I like the integrated aspect of it. The biggest advantage of UiPath is that it not only tests but also integrates with all the other services to offer a complete package. 

Our primary application is built on Windows, so we've faced no significant challenges. However, I think mobile automation is one area where the solution still needs some work. 

I have used UiPath Test Suite for more than five years.

I rate UiPath support a 10 out of 10. They've been fantastic and are always there to help customers. 

Positive

We saw benefits from using UiPath Test Suite almost immediately. We did a proof of concept for about two weeks and put it into production

UiPath Test Suite is a cost-effective solution. Orchestrator is the most expensive UiPath module, costing around $20,000, but you don't need to purchase Orchestrator to use Test Suite. You can buy a nonproductive version that costs about $2,400. It's a better value than other products I've seen. 

I rate UiPath Test Suite a nine out of ten. We started with Test Suite, but now that we have UiPath in place, we can also automate our processes. That's UiPath's advantage. It isn't simply a testing solution. We have the option to scale up our test cases or automate other processes. It's one of the benefits of using an RPA tool for testing. 

UiPath has a few minor areas that need improvement like mobile testing, but they are constantly adding features like AI-driven functionality. I'm optimistic about the platform's potential. 

We use it to automate processes. For example, we can filter or fetch data from an Excel sheet and put it into another file. We can also scrape the data and put it into an Excel sheet or PDF.

We can integrate with multiple technologies such as Java, Python, etc. We can also automate with the Power BI tool. It supports different types of integrations. We are able to integrate with Jira, ServiceNow, etc.

It makes automation easy. To automate with Python or Java, we have to write a lot of code, which is not the case with UiPath. It is very easy to use.

I like the AI Center and Document Understanding features. I also like its interface and the ability to code.

It is user-friendly. The coding part is also fine. They have a portal for learning UiPath. 

It is feature-rich. It has more features than other RPA tools.

It already has many features. No improvement is required currently. We are able to automate most tasks by using UiPath. Its interface is fine. However, its price is a bit high.

I have been using this solution for two years.

It is stable. I would rate it an eight out of ten for stability.

It is scalable. I would rate it an eight out of ten for scalability.

We have 10 to 11 users working with UiPath.

We are also using other RPA tools such as Power Automate, Blue Prism, and Automation Anywhere. We use the latest technology to improve our automation.

We take the customer requirements and analyze them. Based on the requirements, we recommend the solution. We see whether what the client needs can be automated through UiPath or some other solution. Certain things cannot be automated through UiPath. Similarly, certain things cannot be automated through Blue Prism or Automation Anywhere.

With other RPA tools, no test suite is available, whereas with UiPath, you have UiPath Test Suite. With other RPA tools, you have to use Selenium or some other application for testing, whereas, with UiPath, you have UiPath Test Suite, so you can create your test cases.

It is deployed on the cloud. Its deployment is easy. It is not complex.

After we complete the development, we test it in our testing environment. After monitoring and ensuring that everything works fine, we move to the production environment. We create a ticket in ServiceNow with the change request and get approval from the higher authority for the move to the production environment. It takes us three to five days.

It requires some maintenance. 

Its price is a bit high. I would rate it an eight out of ten for pricing.

Most companies are using its licensed version. It has a lot of features such as Document Understanding, AI Center, etc. For simple automations, there is also a community version.

It is a very good solution. People can learn it easily. It is the best solution if you want to automate repetitive tasks and manual operations. 

I would rate this solution a nine out of ten.

Mobile applications are growing in popularity every day, so we need to perform regression tests whenever we add new functionality to our mobile app to ensure that the existing functionalities are still working and that there are no unintended effects from the new feature. To do this, we test one version earlier of the app in every release. We focus on testing the current functionalities. If we find anything broken, we inform our development team and they will fix it before we release the new package. Regarding automation, we have four or five manual testing mandates. UiPath Test Suite is our most useful tool for test automation.

Currently, we only use UiPath Test Suite for our mobile application regression tests, but we plan to add our Internet banking and core banking regression tests in the near future.

We are currently using UiPath for our RPA ecosystem. We saw a demo and decided to purchase it, so I cannot compare it to other technologies. However, our paysite is very strong, and our experience with RPA development in UiPath Test Suite has been easy to manage.

It is faster out of the box than manual testing. It also allows us to run tests after working hours, which is easy to manage because we can schedule them, for example, at 10 p.m. on weekdays. This makes it very easy to manage these types of tests. Additionally, we have four or five mandates in each sprint, and we run these tests automatically.

UiPath Test Suite has helped free up our analysis team's time by saving them about five mandates per week. Previously, they had to run manual testing, but now they can focus on testing new features and analyzing new projects each week.

Test Suite has reduced our maintenance by 25 percent. It has helped reduce our TCO by four mandates each month.

We achieved time to value after three months, once we reached 100 scenarios and the solution became efficient.

When we bought the UiPath Test Suite, we had an agreement with a local partner who provided us with a mobile device farm. This allows us to connect to their site and run tests on different types of devices and operating systems. We manage this very easily, so it is the most important feature of the UiPath Test Suite.

We also don't develop test robots like typing codes; we program them with drag-and-drop features. This is very easy to use and makes it easy to develop test scenarios. These two features are the most amazing aspects of the UiPath Test Suite.

UiPath Test Suite provides developing scenarios, a test manager tool, test robots, and an orchestrator for scheduling and managing test timelines. The test manager component could be improved. For example, when we open a Jira cart for a regression test, it triggers a job on the test manager, but we must then push each test individually in the test manager. We cannot send partial or total tests to run automatically. I have reported this issue to UiPath, and they have said that they are working on a solution.

I have been using the UiPath Test Suite for almost one year.

UiPath Test Suite is stable. We encountered some connection issues, but it was the third-party solution's problem.

UiPath Test Suite is scalable, but our mobile application development departments may not fully understand what it is used for or how it can help them. Sometimes we have difficulty communicating the issues because they request us to automate functional testing, but UiPath Test Suite is not designed for functional testing. It is most efficient when used for regression testing, for which it works 100 percent reliably.

The technical support is good.

Positive

The initial deployment was straightforward and took three and a half days to complete. Two people from our RPA team, including myself, were involved in the deployment part-time.

The price is a bit high. One robot license costs 1,500 euros.

I would rate UiPath Test Suite ten out of ten.

UiPath is deployed across multiple departments, including IT departments, mobile application development, process management, and RPA development. We currently provide services to these departments, but not to our other lines of business.

We have five test manager licenses, but only two people are currently using the test manager licenses.

Sometimes we remove scenarios we have developed or identify points to manage testing more quickly or efficiently. We are doing some maintenance, but it is not required due to the way UiPath Test Suite works.

UiPath Test Suite is really basic and easy to manage.

I highly recommend the UiPath Test Suite. For people not familiar with UiPath tools, I suggest getting a demonstration.

The primary use case of the UiPath Test Suite is testing. Every process could have unexpected issues, so the primary use case is that there is a defined set of steps for every scenario, so you'd probably create different scenarios and data. You can also handle data dynamically because, for the same set of values, you can run that differently for different test data and have mock test flows.

For example, the best use case for UiPath Test Suite is when you have a website where people create an account. For that account, you can create the part with correct values, then you can feed all the values that are out of bound, such as special characters, or you can have a different value entered, which is not accepted so that you can play around with it. Each of the scenarios mentioned helps a lot, so when you get that over to the client, and every time there's a new deployment, the client can just directly run the tree test to ensure that every functionality works well, which helps reduce the support the client would need as well as budget in the long run. The client might have to spend a little longer to develop this, but it's a one-time task, which means that only when something new comes up, you might have to update the test script, reducing the effort to communicate with the vendor or developer back and forth. UiPath Test Suite also helps ensure that the test cases work well, allowing you to go ahead and run the final process and production.

UiPath Test Suite has helped improve my client's organization as the client doesn't have to come back to me or my team multiple times. The tool has reduced the client's need to communicate with me or my company.

At the time of development, the time usually increases by twenty to thirty percent, which includes how my team would develop the test cases. Still, no extra time would be involved later when the client uses the UiPath Test Suite. The client would just need to run the tool or schedule it once a week to ensure the process works well, and won't have to check with my team or company if it's working fine. Even though the bot is failing or there's a design issue, the client just has to check the tool and see if any test script is failing. If the script is not failing, that means there's a data issue from the client's end, which means the client doesn't have to rely on my company to fix it. UiPath Test Suite really helped the client reduce costs. Even though the development costs took a hit initially, it was better for the client in the long run.

I like that UiPath Test Suite is a very helpful tool that many people have not appropriately explored, but as I started my career as a tester, I understand how useful it is. I've used RPA and testing tools for at least two months, and I found UiPath Test Suite a good tool that lets me design scripts and ensure that the client is not worried about the basic process. The tool works as expected and handles one of the most important exceptions in the process.

Using UiPath Test Suite has also been economical for the client, who used to have an RPA admin who managed the processes and monitored whether all worked well. Still, if any issue came up, the client had to come to my team of developers to have the problem fixed. I created the test and the scripts for the processes. The client could also run the bot based on a schedule to ensure the process runs well, each account is up-to-date, and there is no failure in the process, but as soon as an item is flagged, the client has to come to my team. However, with UiPath Test Suite, the client doesn't have to connect with developers or my team, which saves a significant amount of time, and also means needing just one person to manage or handle the processes, rather than being charged every time my team provides help to the client, helping save on costs as well.

UiPath Test Suite can help with the automation you're developing. If I did another workflow, for example, and I want to test it, I can feed it different parameters, as every workflow can have parameters fed into it. UiPath Test Suite can take values from an Excel sheet or data table and show the data or records list, including all the different scenarios. Regarding what the tool can test, it can test anything you can develop from your end. There is no limitation to what UiPath Test Suite can help develop and test.

What I like most about UiPath Test Suite is that it's straightforward, and any user who knows how to use the UiPath Studio can learn how to create a test script in as fast as thirty minutes. There's nothing new you must learn to use UiPath Test Suite because it only has three sections: Given, Then, and When. You divide your script and predefine the values, what will be the input, and what steps you have to take to ensure a specific scenario works, and then you trigger the workflow based on the parameters you provided for the script. Then, you may have to close some applications and wrap up that exhibition for that scenario, so using UiPath Test Suite is very straightforward. The tool is easy to learn, so any user who's probably gone through UiPath's advanced developer certification would have also gone through the UiPath Test Suite. Not everybody implements it, but I feel the tool should be implemented because it's beneficial.

Apart from being developers, my company is also a UiPath partner, which means it has better access to connecting with the UiPath team and getting solutions faster, which I find valuable in the UiPath Test Suite.

I like that the tool shows you how much percentage is covered out of all scenarios you run and the conditions, such as if conditions, wild conditions, or some exception handling.

If something has been missed, you can also tweak and improve the test scripts to ensure every activity is fetched when it's tested so nothing's missed out and ensure all runs fine, which I also like about UiPath Test Suite. In the test field or the test manager, when you go to the architecture, you can also see the percentage and when you run it locally in your machine, which helps you identify whether it needs to be handled.

My impression of UiPath Test Suite having the ability to automate tests from a wide range of technologies is that it has the advantage over other tools. When I started learning RPA, I was working with the testing team, and I wished there was a test kit like UiPath Test Suite at the time. I created an automation to test an application, and compared to that, UiPath Test Suite definitely had an advantage. Even Automation Anywhere and Power Automate didn't have functionalities found in the UiPath Test Suite.

UiPath has also matured a lot in the last two years, as it provides offerings such as task mining, process mining, and document understanding, which may also be found in other automation or RPA tools. Still, UiPath Test Suite is the only tool I've not seen in competitors, which is why UiPath is at an excellent advantage if you know how to use it. It's not difficult to learn, and if you know how to develop in UiPath Studio, you can easily develop and use UiPath Test Suite.

The tool helped free up staff or employee time for other projects because you would not need a separate testing team at all. An employee handling the testing could be cross-trained to do development work. For example, your team could spend more time developing and designing, learning other skills, and improving work.

As for integrating UiPath Test Suite with other lifecycle tools and applications, you can integrate it as long as your application has APIs involved. Say you have to integrate a flow that runs on ServiceNow, which can be integrated with an API. It will work with the UiPath Test Suite. However, if it involves running on a desktop or machine, that would involve UI elements, requiring you to stick to the UI part and develop the workflow instead of integrating it, so that would vary with what type of flow you are looking into. If it's API-based, you can use UiPath Test Suite, but if it's desktop-based, it would be best to use the built-in tool.

The tool helped reduce maintenance, as it has reduced the need to communicate between clients and my company, which helps in terms of maintenance. Maintenance was reduced by thirty to forty percent, mainly from relaying test cases properly and teams following the standards. Maintenance only involves one person and doesn't require the involvement of many people.

UiPath Test Suite also helped reduce the total cost of ownership or testing by thirty percent. The tool only requires more development time initially, but then it does save time in the long run.

An area for improvement in the UiPath Test Suite is maintaining file locations, as that's currently challenging. Say I'm creating a test script, and I create some test data that runs the test script usually created in an Excel sheet. What happens is whenever I import or export from the tool, I have to ensure it contains the Excel sheet with it, which can become a challenge in terms of maintaining the file. It would be better if the files could be on the cloud through a data service within the tool, allowing you to use tables or maybe integrate with an SQL server.

Storing the test scripts is what needs to improve in the UiPath Test Suite, as it's currently a challenge to some extent. Maintaining the files is a bit challenging, especially when you need to keep those locally, because for every workflow you develop, you have to create a test for it, and for each test, you have to create a script, which means you need to create in an Excel sheet.

Another area for improvement in the UiPath Test Suite is its limitation in handling all kinds of variables. It works fine ninety percent of the time, but ten percent of the time, you'd have an issue where you can't just handle it with a string. You'd need some other data type as well, which is currently a limitation of the tool.

I've been using UiPath Test Suite for a year, mainly with my recent client. Not every client usually goes for UiPath Test Suite because, most of the time, the client utilizes a group of testers for manual tests or other tests, in which the client hires testers to do the testing and then validate the results. Most clients do not follow the standard process, so it varies from client to client, but my experience with UiPath Test Suite comes from one client who specifically wanted to follow the standard process and ensure that the data is up to the mark.

UiPath Test Suite has been pretty stable ninety percent of the time. Stability-wise, the tool can be unpredictable ten percent of the time because the same workflow running with the test case can be a problem.

For example, when using the Excel sheet, the challenge is that every value you feed into it must be a string. If you change the parameters or variable type to an integer or any other kind, it can't handle it, which could affect stability ten percent of the time.

There's no issue with UiPath Test Suite scalability-wise. If the area for improvement on storing scripts locally is addressed, then the tool can be scaled to any number without issue.

For UiPath Test Suite support, I've handled communicating with support for some of the client's users, and the team has been very helpful and has been doing follow-ups on time.

Some issues can be solved via email, while some require a call, and I usually get the calls scheduled quickly. Support for UiPath Test Suite has been very good, so I'm rating support eight out of ten.

Positive

I didn't use a different solution before UiPath Test Suite.

Deploying the UiPath Test Suite is straightforward. Within twenty to thirty minutes, you'll be able to learn how to do it, as the process is not complicated. The tool is straightforward to develop and deploy. It's similar to deploying any other process on UiPath Studio. You have the option to either publish the solution or the test cases.

The deployment of UiPath Test Suite only took a matter of seconds because you just had to click "Publish." You go to the UiPath Orchestrator and run the script. The deployment is not complicated in any way.

As UiPath Test Suite is included within the UiPath Studio and is not a separate application, installing it, giving permissions, and logging into your account on your local machine doesn't take more than a few minutes.

I wasn't involved in the negotiations for the UiPath Test Suite, so I have no information on its pricing.

UiPath Test Suite is developed on-premises or on your local machine. Once you've completed the development, you deploy it on the UiPath Orchestrator. Within UiPath Orchestrator, there's a testing tab with test scripts that you can run locally, but the target or vision is to develop it locally and run it on the UiPath Orchestrator.

The client has about ten to fifteen employees using UiPath Test Suite for automation, while at least two people use it for testing, which saves some time and effort.

In terms of maintaining UiPath Test Suite, if an automation needs an update or UiPath Studio needs to be updated, then UiPath Test Suite would also need to be updated.

To anyone who'd say that their automation testing process could be too complex for UiPath Test Suite, I'd say they would still want to see what part of it can be tested. Sometimes, there could be a challenge where you can't create a test script for a particular scenario. However, that wouldn't apply to all scenarios. Though you may not be able to cover one hundred percent with UiPath Test Suite, the tool could still cover at least seventy to eighty percent of the scenarios, including complicated ones that are pretty difficult to handle. Still, most of the time, those won't be an issue with UiPath Test Suite.

I would recommend the UiPath Test Suite to others. If you want to get comfortable with it, go ahead and create a test case for one workflow and see how it works. My advice to others is to test the tool out. I would definitely recommend it as no other solution has this offering, and I find the UiPath Test Suite very useful.

My rating for UiPath Test Suite is a solid seven. I see a lot of room for improvement, but UiPath is going in the right direction.

My company is a partner of UiPath, working with multiple enterprise clients.

We use the solution in our testing environment. It's for integrating and developing entire workflows for different test cases. 

We do have multiple scenarios integrated with UiPath. For any particular application, every time a release goes, we need to host the test and those scenarios. We are examining the scenarios and getting reports. We are using the same report to publish it for the wider audience. 

It's helped reduce the amount of time it takes to perform certain activities. It's also meeting the ROI of the organization from a budgeting perspective and utilizing fewer resources. The automation information it provides is very useful.

Getting a bird's eye view of testing scenarios is quite useful. The console, in a single pane, allows us to understand where we are in the testing environment. 

It can automate different tests from different technologies. We can integrate it easily across multiple technologies. Many are supported, which wasn't the case before. It helps with testing and integration across all our technologies making it easier.

Using UiPath processes, we've saved around 50% to 60% of our time in terms of working through processes. 

It works well with various lifecycle tools. There are open APIs available that you can integrate with. 

There isn't much maintenance needed unless there is a change in requirements. UiPath has a patch suite that helps reduce maintenance.

The solution has reduced our total cost of testing. 

They could improve the visualization of the product. We'd like them to improve the visibility on the dashboard and also ensure live scenarios can be viewed.

I've used the solution for five to six years. 

I'm not sure how many people are using the solution.

The solution allows us to scale our automation. It reduces the time it takes to handle tasks. 

I've found technical support to be good. 

Positive

We were doing a lot of manual processes previously. 

The initial setup was very easy. 

We have witnessed an ROI. We have noted the value of using this particular tool. It's worth the money. 

The solution has helped the company with respect to functionality. It's not about the cost. From a cost perspective, it's worth the price. 

I can't speak to having evaluated any other solutions previously. 

I'm a customer and end-user. 

We're using Javascript to automate.

If someone thinks their automation testing is too complex for Test Suite, I'd let them know that it's very good at building automation and performing computer testing. I'd recommend it to anyone - even if they have complex processes. 

I'd rate the solution nine out of ten.