We had tried this (unit-testing) within the REFramework in the initial stages of our CoE establishment. To keep the development and test phases separate, we choose to use Test-Suite instead where we can test all the activities we developed for a given project and perform integrated test (similar to the flow of process we are automating).
We modify the UiPath test-suite to our use case and write outputs to a custom excel file depending on the process we are automating.
The “test cases” in the test-suite can also further be tested using a “test robot” license on a prod-like VDI or alternatively in AzureDevops (Tests) before deployment.
Our final test phase is to run the robot for the suggested Cochran’s Sample Size given the expected cases for the robot (population). This sample size gives us number of test cases to be run before we can represent the outcome to the entire population of robot cases. We require a minimum of 90% test cases are success. We try to keep the
psample proportion to 0.5 as we have no observed evidence towards success or failure in the testing population.
We run this test in REFramework process on NonProduction license so that we have a robust robot which tackles production-like environment and data. If we do not meet the success ratio, then we have to identify where the most failures originated, fix it and run the test for the same sample size.
But if you have regime for unit-testing, the inbuilt Tests folder in the REFramework is a useful tool.