Share this page

# Manual Testing

You can open a mobile device or browser from the lab for manual testing. These sessions can be recorded as video files. You can also use the step recorder to record steps on a device and then use this to submit a defect directly to OpenText Software Delivery Management.

This section covers manual testing on a device. For manual testing on a cloud browser, see Browser lab.

In this topic:

## Start a testing session on a device

You can conduct a manual testing session on a device in the lab.

To start a manual testing session:

1. Go to: `http/s://<OpenText Functional Testing Lab server IP address>:<server port>` and log in with your credentials.
   OpenText Core Functional Testing Lab: To access the lab console, go to the SaaS URL provided to you, and log in with your credentials.
2. On the Devices tab, open the device as follows.

   View | How to open
   --- | ---
   Card | Hover over the device card and click the Open device remotely button .
   List | Select the device and click Open device remotely in the device list toolbar.

   If video recording of test sessions has been enabled by your administrator, the recording of the session starts when you open the device remotely. For more details on this setting, see File storage settings in Administration settings. For details on how to view or download the video, see Test results.

Back to top

## Record steps

Use the step recorder to record steps during an exploratory test session on a device.

To record steps:

1. In the device access window, click the Exploratory Testing icon . By default, this icon is located in the right-hand pane.

2. Click the Record button in the toolbar. The recording session starts.

3. Interact with the device. Actions performed on the device are added as steps, together with a screenshot.

   The date and time that a step was performed is added after the step in the zip file, and in the defect.

Note:

- A maximum of 30 steps can be recorded in an exploratory session.

- Steps that you perform are captured and snapshots are saved automatically. As a result, device responsiveness is slower than when actions are performed on a device without recording.

1. Perform additional actions from the exploratory test toolbar.

   Button | Details
   --- | ---
   | Pause recording. To resume recording after pausing, click the Record button .
   | Stop recording.
   | Download a zip file of the steps. The zip file includes screenshots and the following text files: device_details, recorded_steps, and device_logs. You can use this to create a test case.
   | Submit a defect to OpenText Software Delivery Management. For details, see Submit defect.

To add or delete steps, and to select screenshots, see Edit steps.

Back to top

## Edit steps

During a session recorded with the step recorder, your test steps are listed in the exploratory testing pane. You can add steps, delete steps, and select screenshots for steps.

To delete steps:

1. Select the step/s to delete, or click Select All.

2. Click the Delete button. When steps are deleted, the numbering of the steps and screenshots is adjusted accordingly.

To add a step:

1. Click the Add Notes button to add a note or step. A screenshot is taken automatically when the button is clicked. A placeholder for the note is added as the last step, accompanied by the screenshot.
2. Start typing. Click the checkmark to confirm the text and to add the note.
   The note is added with a /// prefix to indicate that it was added manually. This prefix cannot be deleted.

To select screenshots:

By default, screenshots are included in the zip file for most steps. Certain steps, such as installing or uninstalling an app, do not include screenshots.

You can exclude screenshots as follows.

Action | How to
--- | ---
Exclude all screenshots | Click the Exclude all screenshots button in the toolbar above the steps to exclude screenshots for all steps.
Exclude a specific screenshot | You can remove screenshots for specific steps. Click the Include screenshots button to switch off the screenshot option for a specific step.

Back to top

## Submit defect

If the integration with OpenText Software Delivery Management is enabled in Administration settings, you can submit defects during a recorded manual testing session. For details, see Defect Tracking System integration.

To submit a defect:

1. Click the Submit Defect button .

1. The connection is checked. A new tab opens to log in to OpenText Software Delivery Management. After successfully logging in, or if you are already logged in, you can close the tab.
   If your OpenText Functional Testing Lab username is different from your OpenText Software Delivery Management username, you are prompted to provide your OpenText Software Delivery Management username.
2. In the Submit Defect dialog box, give your defect a name, and select the OpenText Software Delivery Management workspace to which to submit the defect. Only workspaces to which you have access are listed.
   The description field of the defect is automatically populated with the device details (manufacturer, model, ID, version) and the numbered list of steps.

   Note: The workspace is saved and set as the default for the next defect that you submit.

   If you included screenshots for steps, these are included in a zip file that is automatically attached to the defect. Screenshot files are named according to the step number. The zip file also contains the device log file.

3. Click Save to submit your defect.

Back to top

## Interact with the device

You can interact with a device during a manual testing session and perform the following actions:

- Simulations: Fingerprint and Face ID simulation, Photo and video simulation, and QR code and barcode simulation.
- App interactions: These actions include installing and launching apps. For details, see Device actions & simulations.
- Other actions: These actions include changing your orientation, zooming in and out , or sending text to your device. You can also view information about the device. For details, see Device access window.

Back to top

## Live log

Use the live log to examine the device log in real time and to investigate issues encountered during testing.

To use the live log:

1. In the side pane of the device access window pane, click the Live log button .
2. Select either an application log, or the device log. For application logs, select one or more apps from the list of OpenText Functional Testing Lab apps installed on the device.
3. Click the Start button to start the live log. Use the dropdown menu in the pane to select the logging level: debug; trace; info; warn; error; or fatal. Use the toolbar for auto-scroll, text wrap, download, and copy options.
4. Click the Stop button to stop the live log.

Note: Only the last 1000 lines of the log are displayed in the pane. If you need to download the full log, use the Download device logs option.

Back to top

## Accessibility testing

You can test accessibility using VoiceOver or TalkBack audio, or use the Accessibility Inspector to verify the VoiceOver/TalkBack output (text), attributes, and the navigation order of accessibility elements. For details on Accessibility testing, see Accessibility Testing.

Back to top

## Known issues with recorded sessions

This section details known issues with recorded sessions.

- A screenshot of the last action is not recorded and not saved to the report log.
- When recording on iOS devices, hybrid/web is supported only for iOS version 13 and higher.

Back to top

## Manual testing with Sprinter

Sprinter is a software solution for interactive testing, including testing mobile applications. Sprinter provides advanced functionality and tools to make interactive testing more efficient and effective.

When you start up Sprinter, you select whether to log in with your ALM credentials or connect to OpenText Functional Testing Lab.

Installation prerequisites

- Enable browser cookies.
- Clean devices of any apps installed using earlier versions of OpenText Functional Testing Lab.

Install Sprinter

Install | Visit the Sprinter page in the AppDelivery Marketplace.
Help | Open the Sprinter Help Center.

Back to top

https://admhelp.microfocus.com/Functional Testing Lab 8942
Tips to improve your search results... OpenText™ Functional Testing Lab for Mobile and Web Help Center OpenText™ Functional Testing Lab Help 25.2 All View Local Help Center View Online Help Center Version: