From Test Authoring to Real Devices: How UiPath and Digital.ai Work Together

Your organization may already use UiPath for automation or testing beyond mobile. Expanding that practice to mobile is a natural question. Or your team may be choosing an authoring tool for a new mobile testing program. Either way, the workflow you create needs somewhere to run. 

UiPath Studio and Digital.ai Testing can provide a connected path. UiPath is where the team builds mobile automation workflows; Digital.ai provides access to the devices on which those workflows run. 

Start with how the test is built 

In UiPath Studio, mobile automation is built with activities for interacting with an app and checking its behavior. A test author defines the journey: open the app, perform actions, and verify the expected outcome. The workflow still needs maintenance as the app changes, but it gives the team a place to develop and update that logic. 

UiPath describes mobile automation in three layers: Studio and activities, an Appium server, and the target device. That middle layer matters. Appium makes it possible to direct a UiPath workflow to an iOS or Android device beyond the author’s desk. UiPath supports an external Appium server, so the device can be part of a remote device farm. 

Connect the workflow to Digital.ai Testing 

Digital.ai Testing provides the device environment and Appium endpoint. In UiPath Studio, the team creates a Mobile Testing project and configures the connection for the app and device it wants to test, whether iOS or Android. 

For organizations already using UiPath, this extends a familiar authoring approach into mobile. Teams choosing UiPath for the first time can use the same connection. In either case, test authors build and maintain their workflows in UiPath, then run them through Appium on devices in Digital.ai Testing. The team still decides which user journeys and devices matter most. 

Choose the device environment for the way you operate 

The device decision is not identical for every organization. Some teams need specific real device models and operating system versions available on a predictable schedule. Others need to keep testing infrastructure inside their own environment. The question is which requirements belong to the release process and which deployment can meet them. 

Digital.ai offers dedicated device pools selected for an organization’s needs. With its private SaaS deployment, the environment is single tenant and Digital.ai manages the hosted lab, including device maintenance. An on premises deployment keeps the lab in the customer’s environment; the customer manages the physical infrastructure while Digital.ai provides the platform software, setup assistance, and updates. 

Dedicated access can be valuable when a team needs a particular configuration ready for scheduled runs. It is a choice to evaluate against the team’s existing lab and coverage needs, not a prerequisite for every mobile test. The important thing is that the tests can reach the intended devices reliably. 

One workflow, from authoring to execution 

The integration answers a practical question: how does a UiPath mobile test get from its author to a device that matters for the release? Appium provides the connection. Digital.ai provides the device environment. Your team retains the decisions about which journeys to test, which devices to cover, and how to maintain the workflows. 

If you’re evaluating this approach, start with one important mobile journey and the devices it needs to run on. Watch the UiPath and Digital.ai integration video. 

Pt 3 of our UiPath blog series shows how one team extended its existing UiPath strategy into mobile testing.