Share this page

# Run tests on terminal emulators

This capability is relevant only for Windows.

OpenText Functional Testing for Developers can test terminal emulator applications that support HLLAPI as well as those that do not, such as emulator sessions configured to work with the VT100 protocol (using Text-only mode).

In this topic:

## Windows and screens

When testing, OpenText Functional Testing for Developers distinguishes between the window of the terminal emulator and the screens in the host application.

The terminal emulator window consists of the frame, menus, toolbar, and status bar of the terminal emulator itself. This window remains constant throughout each terminal emulator session.

The terminal emulator screen refers to the area of the window in which the application is displayed. Each time the host responds to user input to the application, the screen changes.

OpenText Functional Testing for Developers includes preconfigured settings for several terminal emulators and enables you to configure the settings for most others as well.

For configuration details for the supported emulators, see Configure your terminal emulator for testing.

For a full list of supported terminal emulators, see the Support Matrix.

Back to top

## Set up OpenText Functional Testing for Developers to work with the terminal emulator

To set up OpenText Functional Testing for Developers to work with your terminal emulator:

1. Ensure that the runtime engine is up and running.
2. From the OpenText Functional Testing for Developers icon on the system tray, click Settings to open the runtime engine Settings dialog box.
3. On the Engine tab, under Add-ins, select Terminal emulators.

4. Configure your terminal emulator's details:

   1. Run <Installdir>\bin\TeConfigurator.exe.

   2. In the Terminal Emulator Configurator dialog box that opens, do one of the following:

      - Select a preconfigured terminal emulator from the list. See also Copy existing terminal emulator configurations.

      - Click Open wizard and follow the onscreen instructions to add or modify a terminal emulator configuration.

        Note: On the last page of the wizard there is an option to save the configuration. You may want to use this option if you want to copy the configuration to another computer.

        By default, the configuration file (.reg) is saved in the <Installdir>\dat folder.

        Close and reopen the Terminal Emulator Configurator to refresh the Terminal Emulator list.

   3. (Optional) To define the area of the emulator screen to be displayed, select the emulator in the list, and under Screen label, define the start row and start column, and how long the area should be.
   4. (Optional) Click Adjust configuration to fine-tune the settings of the emulator that you have selected.

5. Click OK to save the configuration.

6. Configure your terminal emulator to work with OpenText Functional Testing for Developers. For details, see Configure your terminal emulator for testing.
7. Restart the runtime engine.

Back to top

## Supported test objects

The following Terminal Emulator test objects are supported:

Test Object | Description
--- | ---
TeField | A terminal emulator field that fully supports HLLAPI
TeScreen | A terminal emulator screen that fully supports HLLAPI
TeTextScreen | A terminal emulator screen that uses text-only HLLAPI or does not support HLLAPI
TeWindow | A terminal emulator window

For more details, see the Java SDK Reference, .NET SDK Reference, or JavaScript SDK Reference.

Back to top

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