Connecting to OpenText Application Quality Management

When connecting, OpenText Functional Testing connects with a "super user" permission level, regardless of the specific user permissions assigned to you in OpenText Application Quality Management. This enables you to use all aspects of the application regardless of the privileges allotted to you for working in an ALM project.

Note: This section is only relevant if you have enabled communication between OpenText Functional Testing and ALM project by setting the relevant DCOM settings. For details, see DCOM configuration settings.

Default access level

The ALM project uses the parameter ALLOW_LEGACY_INTEGRATION_MODE. By default, this parameter is deactivated, and your activities in OpenText Application Quality ManagementALM by OpenText Functional Testing are limited by the assigned user permissions in your ALM project.

For full details on the parameter ALLOW_LEGACY_INTEGRATION_MODE, see the OpenText Application Quality Management Help Center.

In addition, if you are running GUI tests from the ALM Test Lab, you must select the Allow connections from computers running any version of Remote Desktop (less secure) option in the Windows Remote Settings (Control Panel > System > Remote Settings) . Failure to enable this option will result in the test run stopping when the Remote Desktop session is disconnected.

Connecting to OpenText Application Quality Management using Single Sign-On (SSO)

To connect to an ALM server that requires Single Sign-On (SSO), you provide the SSO credentials.

When you run tests manually from OpenText Functional Testing, you enter the credentials directly in an SSO login page provided by OpenText Application Quality Management. OpenText Functional Testing never stores these credentials.

When you run OpenText Functional Testing using an automation script and connect to OpenText Application Quality Management, you must enter the credentials in the script. The credentials you enter are stored in a text file. We therefore strongly recommend that you always encode this information before entering it in the script. For details, see the Automation Object Model Reference.