You can turn Tricentis Tosca TestCases into RPA Studio Bots.
This is only possible for TestCases that you created with the Engines 3.0 listed in "Supported technologies".
TestCases vs. Bots
Not every TestCase makes a viable, stable Bot.
TestCases are used in test environments. They explore and test the impact of changes that you make to your systems.
Bots navigate your production environment. They automate actual business processes and work with live data.
With a Bot, you neither test nor explore. The Bot should work exactly as you designed it, without incident. Checks and verifications in Bots are usually very different from checks and verifications in TestCases.
So take a good look at your TestCase to see whether it will make a good Bot.
Import TestCases into RPA Studio
To turn your Tricentis Tosca TestCase into a Bot, follow the steps below:
If your TestCase contains an element that RPA Studio could not import, the Bot adds a Placeholder instead.
Get your new Bot ready for production
After the import, go over your new Bot and modify it to get it ready for production (see "TestCases vs. Bots" above).
Pay special attention to the following:
Conditions
Conditions in Tricentis Tosca can be complex and include several TestSteps. This is not true for Bots; Bots only check one Step per Control Expression.
When you import your TestCase, RPA Studiogroups your Conditions.
If you import Reusable TestStepBlocks, RPA Studio turns them into separate Bots.
Note that RPA Studio does not support Business Parameters.
You need to remove all references to Business Parameters from your Bot Steps.
Recovery
RPA Studio cannot import Tricentis Tosca Engines 3.0 Recovery. It does, however, offer clean-up procedures for Bots as described in "Define clean-up procedures".
Instead of Recovery, you can define clean-up procedures for your imported Bots.
What's next
Once you have converted your TestCase into a viable, stable Bot, you can test it.