Run Mobile App tests
Sprinter's integration with OpenText Digital Lab (formerly UFT Mobile) lets you run your mobile app tests on a variety of devices.
You create your mobile test in Plan mode. For details, see Create a Test for mobile apps .
Make sure you have access to a Digital Lab sever.
Upon startup, Sprinter prompts you to connect with ALM, ValueEdge and ALM Octane, Digital Lab, or a UFT license. For details, see Log in to Sprinter.
- If you connect via Digital Lab, enter the server details and credentials in the Digital Lab log in area.
- If you log in with ValueEdge and ALM Octane or a UFT license, provide the Digital Lab credentials after Sprinter opens, in the Settings dialog box.
If you log in with ALM, then:
- If the ALM project has the Digital Lab extension enabled, Sprinter automatically retrieves the Digital Lab server credentials from the project. You will not be able to modify them in Sprinter.
- If the ALM project does not have the Digital Lab extension enabled, Sprinter will not retrieve the credentials from the ALM Site Administration. In this case, provide the Digital Lab credentials using the Settings dialog box:
Click Settings .
Choose authentication method:
- Basic authentication. Connect via a username and password.
- Access key authentication. Connect via execution access key.
- If the Digital Lab server was installed with secure access (https), select Use SSL. If you did not enable this option, and the Test Connection failed, try selecting this option. When working with Digital Lab through SSL, client machines must have an SSL certificate installed in the Trusted Root Certification Authorities category.
- If your connection to Digital Lab is through a proxy server, click Proxy Settings to provide its details.
This section describes how to manually run a mobile test from Sprinter.
To run a manual mobile test:
- In Run mode, enable Power Mode and open your test.
- Click on the Application Settings button for Power mode.
In the Applications tab, select a mobile app from the drop down list or click Add to add a new one. The Add Application dialog box opens. Click the Mobile App icon . (If you logged in via Digital Lab, only the Mobile App button is shown.)
- Enter a name for the application.
To test a native app, system app, or the home screen, click Select App. The Digital Lab wizard opens. Follow the three wizard screens to select a device, app, and test options. For details, see the Digital Lab wizard.
Note: If you selected the packaged version of an application for recording, you need to select the packaged version for replay.
- To test a web application, click Select Browser from the Select App dropdown. The Digital Lab wizard opens. Follow the three wizard screens to select a device, browser, and device metrics. For details, see Digital Lab wizard.
- Click Save and Close at the top right corner of the wizard window.
- If you are working with SAPUI5 technology in mobile applications, select SAPUI5 technology. Sprinter launches the application with the SAP UFT agent in order to record all controls.
- Click Save App Settings in the Application tab.
- In the main window, open a test for execution and click the Run button. The Mobile remote view window opens with the Control Panel.
- Interact with your device and enter simulations. For information, see Create a Test for mobile apps .
End your test run, and proceed as you would with any other test.
This section describes how to manually run a mobile test from ALM.
To run an ALM mobile test:
- Make sure you have enabled the ALM Digital Lab extension in ALM. For details, see Log in to Sprinter.
- Click on the Digital Lab icon in ALM's Execution Grid or Test Instance Details dialog box. The Digital Lab dialog box opens.
- In the Digital Lab dialog box, select a test type, Mobile or Web, and click Open Wizard. Follow the wizard screens to select a device, app or browser, and device metrics. For details, see Digital Lab wizard.
- Save your choices and run the test.
When you run a test, Sprinter creates an Application entry for the app used by your test, for each test instance.