UiPath Studio Community Preview was just released last week with new testing capabilities. This will allow you to create robust and flexible Test Cases for applications and your automated processes.
To run those Test Cases at scale, we have made those capabilities available also on Orchestrator.
As soon as you publish your Test Cases from Studio Pro the first time onto Orchestrator (via ‘Publish Tests’), and you have converted the uploaded package into a process, your Test Cases will reside in this section. This is meant to be your inventory of available Test Cases for execution. For a better overview, you can filter here by Project and App Version.
After uploading your Test Cases to Orchestrator you might want to run them on 1-n of your robots. Therefore we provide you the Test Set section, where you can group together several Test Cases to run them together (e.g. you might want to create a Regression Test Set, including all your Test Cases, or a Smoke Test Set, intended to be run with every code checkin).
To create a Test Set, simply (1) navigate to the Test Set section, (2) click , (3) give your Test Set a name and description, (4) select the environment you want to run it on, (5) filter by project and version and (6) select your Test Cases.
To run your previously built Test Set, select the button on your Test Set. This will immediately start the execution, and navigate over to the Test Execution section, where you can monitor the progress.
Test Cases queued have the state ‘Pending’, run Test Cases are either ‘Passed’ or ‘Failed’. During the execution you can anytime cancel Test Cases, or the entire Test Set.
To make it as easy as possible to analyze failed Test Cases, we provide you with additional information such as the detailed log and the screenshot of the robot, taken when an assertion has failed.
Additionally, to starting a Test Set manually, it is also possible to schedule the execution of a Test Set. This allows you to e.g. setup reoccurring execution of your Test Set once per Sprint.
To create Test Cases and publish them to Orchestrator, you require Studio Pro, which can be download from the Community preview page.
To run your Test Sets, you have to have 1-n robots setup, of type ‘Testing’. This can be done by adding the Testing license to your service on portal