What is your primary use case for UiPath Test Suite?

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.

I worked on a project for a bank that involved mortgage facilities for leasing motor vehicles. Clients approach the bank for financing, providing details about their needs. The process is divided into groups, with each group handling specific tasks. I implemented UiPath test cases to simulate the process, including customer registration, bank response, mortgage eligibility, and more. These test cases are executed in a long-running fashion and are currently operational. In UiPath Test Suite, we create test cases in Studio and then publish them to Orchestrator. The publishing process allows us to disable unnecessary test cases, reducing the overall project size. After publishing, test cases are organized into Test Suites in Orchestrator. These suites can be executed in batches, allowing for daily testing and monitoring. The Test Suite manager in Orchestrator provides a dashboard with a pie chart showing test case success and failure rates. This tool helps analyze test results and identify areas for improvement. While the Test Suite manager is primarily for checking and inspection, it also allows for editing, reading, and running test cases. By dividing large processes into smaller parts, UiPath Test Suite becomes a valuable tool for testing and quality assurance.

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 use UiPath Test Suite to test the workflows designed in UiPath Studio.

UiPath is used for a couple of workflow-related activities. We use it for onboarding and other HR tasks. When an employee comes to the organization, we use UiPath to validate their details or whether the employee ID has been created. After verification, it will trigger an email to the IT department to configure a desktop based on the employee category. Once it's approved, we close that ticket. We use it as a ticketing process checking mechanism. In a few areas, we are also using it for testing. We execute some of the test cases through UiPath. We use UiPath Test Suite to decrease the time to market, which means reducing the test cycle time and for attended execution. We had 10 to 15 people using it in the previous version, but now we only have three users at my current organization.

Historically, we have used the UiPath Test Suite to perform regression testing during third-party web-hosted application upgrades. When a new version of our platform is released, we leverage the product to execute our standard test scenarios and verify the stability of the new release, ensuring that no existing workflows or integrations are negatively impacted.

I work with the solution in order to automate tasks in our company. It works alongside our Jira product. We can coordinate with Python to automate tasks and use AI.

We mainly work with web as well as desktop automation. One of our use cases was to raise a ticket from the web portal to the ServiceNow defect management tool, and another was the need to interact with a Linux server through PuTTY. We use UiPath to run different ETL jobs.

We use the product for RPA and application testing.

I primarily use the solution for websites. It can take some details from users within multiple scenarios. If I were to pull the data manually, it would take a lot of time. Instead, we can create a bot in UiPath and do testing in far less time.

We just need to make sure that the test cases are created, to be able to validate those results as per the expectations. We then provide the results to the respective teams. There are a lot of integrations for the Test Suite as well with Jira and DFS, et cetera. That's where we would be able to integrate with the test cases and then provide the test cases as well.

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 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.

We use the solution to automate tests. We have different teams implementing different applications. My responsibility is to use it on end-to-end tests.

We use the solution for supply chain management use cases. We can do test automation on the UiPath process automation tool. We used it for logistics orders and distribution projects. We have different applications there. We automated 12 applications.

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.