What needs improvement with UiPath Test Suite?

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.

UiPath Test Suite, a feature within Orchestrator, is a useful tool for testing automation processes. However, accessing the full functionality of the Test Suite manager, including the dashboard, requires a tenant license. This can be a barrier for users without technical expertise. While the community version offers free features like document understanding API calls, the Test Suite also provides limited free access to user community support. Still, access should be expanded as it can be crucial for learning and understanding the tool. Regarding framework comparison, the RE framework in UiPath offers a structured template for process automation, including exception handling. However, the Test Suite framework needs similar exception-handling capabilities. This can require additional customization for effective application handling.

The solution can cost more than other options.

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.

The reporting could be improved. Often, we need to email a report to higher management, we can directly get the report from there. Also, the error reporting could be better. Building an automation test case from manual cases is easy, but sometimes we feel the process can get lengthy because we cannot create customized functions and the predefined ones are unsuitable for the particular purpose. We need to do a workaround that involves extra steps. I am unsure how UiPath will help with complex processes because they typically have multiple layers of various technologies. It also depends on the data synchronization. For example, if I have posted something in the front end, how long does it take to be reflected in the back end? That also matters because it's passing through different layers. End-to-end automation will be a little bit tricky because there are multiple front-end and back-end software involved. It is easy for either front-end or back-end testing. If we include the back end and front end to create an end-to-end scenario, it will be difficult because sometimes there are different databases and layers connected.

UiPath could further enhance its functionality by simplifying the test case creation process within Test Suite. One way to achieve this is by leveraging AI to analyze existing workflows and automatically generate or recommend suitable test cases based on that analysis. I understand that UiPath is already working on solutions to convert requirements and test cases into automated testing scripts. However, for organizations with numerous pre-existing workflows, the ability to automatically analyze these workflows and generate corresponding test scenarios and cases would be invaluable in onboarding new use cases onto the platform.

We'd like to see the solution integrate with more code or local frameworks. We'd like to see it work closer with AI. It would help enhance UiPath.

I would like to see users have the ability to add their own healing features, such as activating object-healing processes. If they could add that feature, that would be beneficial. It would be something like a rescan. With Selenium, there is a plugin called Healenium, which helps automatically detect changed properties of objects. With one click, it automatically updates the object repository with the changed properties. I would like UiPath to add that capability. It should be able to rescan a page and report to the user the properties that have been changed, and then allow the user to decide which properties they want to update in the object repository.

UiPath needs to improve its Test Manager feature. Defect management and reporting also need improvement.

I have not noticed the solution missing any features. I'd like the solution to be even more automated.

I don't rate its ability to automate very well. There are other tools that are doing great work. For example, Selenium is a product that does absolutely tremendous work with test automation. It provides continuous integration and improvement with different technologies and tools. I'd rate Test Suite as 6.5 out of ten in terms of its automation capabilities. Not many organizations would be willing to use UiPath as it would be an additional tool and the majority of organizations already are using Selenium or other automation tools. It's difficult at times. The adaptability of the solution could be better. You cannot use UiPath Test Suite as a silo product. You would need to use it in relation to their products.

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.

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.

We monitor the runs on Orchestrator. Orchestrator is not easy to use or understand. We almost need to have certification to use it.

The product releases sometimes have issues. In the past, I have provided points, such as exporting to the external file and getting reporting in an Excel file. That cannot be done yet. I don't recommend UiPath for third-party tools. I don't see the value in that. There are, for example, still a lot of issues when integrating with Jira. There were just too many scenarios to integrate.

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.