My team currently uses OpenText UFT, selenium, and some other automation tools to test and we have developed our own automation framework using C# and Visual Studio. It provides standardized logging, reporting, test structure, etc, and it uses the automation tools C# libraries but we wrap them in our own code to make them easier to use, add functionality, etc.
I’ve only just installed UiPath on my machine but I’m curious if it has C# API libraries that we could add to our existing framework solution and build with or if it’s the kind of tool that basically needs to be used on its own.
We assume that a particular modelling was done within UiPath and this is to call / integrate
Therefore we have options like ORC Rest Api, CLI, Webhooks
When the Question is about a programmable consumable SDK that can be used within your code we would recommend to check if the risk of reinventing the Wheel is fully addressed when followed-up the above mentioned intention
I don’t have any existing UiPath modelling, I’m more looking to see if I can swap out OpenText UFT (and the existing UI automation I have built with it) and use UiPath instead. We wouldn’t be looking to develop or build anything directly in UiPath, but would like to in theory add a UiPath SDK into our existing solution and build off that instead…essentially our standard is to force any automation tool into our existing framework instead of using a bunch of different tools in different ways.
I’ve done this before with selenium and it took maybe 4 or 5 days of development effort, just to add all of the required code to our framework so that developers could start building UI automation test cases with it. I’m assuming UiPath would be more complicated. If it’s not possible, that’s fine. If it’s possible, but lots of work, I might just stick with UFT.
This statement reinforces more your intention, which we had guessed
Lets ignore other facts and drive it visionary
A help section at the docu site: UiPath for Developers: C#, Java…
A tutorial like
myUIPathApp = new UiPathApp()
myUIPath .Add(…
myUIPath.Run(…
you will not get directly
Kept in mind:
that it is based on the Windows Workflow Foundation
we can find libraries, assemblies
we can hack statements like below
Can encourage us to think further on this base and direction.
However, when it comes to execution, the picture must be thought further so that the executing component can understand your and the wrapped UiPath code.
To pick up again
drive it
Now is the time to wait for further opinions and to move technical barriers at least 1 millimetre further away
