OpenText Application Quality Management

Relevant for: GUI tests and components and API testing

Integrating OpenText Functional Testing with OpenText Application Quality Management enables you to store and access tests, components, application areas, and resource files in an ALM project, when OpenText Functional Testing is connected to OpenText Application Quality Management.

Overview

OpenText Application Quality Management helps you maintain a project of all kinds of tests (such as tests, components, business process tests, manual tests, and tests created using other ADM products) that cover all aspects of your application's functionality. Each test or component in your project is designed to fulfill a specified testing requirement of your application. To meet the goals of a project, you organize the tests in your project in unique groups.

OpenText Application Quality Management provides an intuitive and efficient method for scheduling and running tests or components, collecting results, analyzing the results, and managing test and component versions. It also features a system for tracking defects, enabling you to monitor defects closely from initial detection until resolution.

OpenText Functional Testing Add-in for ALM

If you have the OpenText Functional Testing Add-in for ALM installed on your computer in addition to OpenText Functional Testing, you can create and edit tests and components directly from OpenText Application Quality Management.

After you have created and edited tests and/or components, you can run and view the run results directly in OpenText Application Quality Management.

For details on installing the add-in, see Additional OpenText Functional Testing-related installations.

Supported integration

When OpenText Functional Testing is connected to OpenText Application Quality Management, you can:

Option	Description
Create tests, components, and resources and save them in your ALM project.	You can save test and components in your project and thereby make them accessible to multiple users. Any changes made by any user are then saved and updated for all users of the test.
View the contents of your tests.	This can help you decide if you want to run a test as part of a test set. Note that the Test Flow in OpenText Application Quality Management and the canvas in OpenText Functional Testing display only the actions that are run when the currently selected test runs. This means that if a nested action is commented out, for example, that action is not displayed in OpenText Application Quality Management or in the OpenText Functional Testing canvas. You can uncomment it in the OpenText Functional Testing Editor when needed.
Run your tests and components and view the results in OpenText Application Quality Management.	In much the same way as saving a test in OpenText Application Quality Management enables all users to use an see the changes, running a test in OpenText Application Quality Management enables all users of the ALM project to see the run results of a particular test. You can also use these run results to automatically or manually add defects to your ALM project.
Associate a test, an API component, or a GUI component's application area with external files stored in the Test Resources module of an ALM project	When you save the resources files for a test or component in your ALM project, it enables you to save just one copy of the resource and link it to multiple tests or components.
Associate external files for all tests or for a single test.	For example, suppose you set the shared object repository mode as the default mode for new GUI tests. You can instruct OpenText Functional Testing to use a specific object repository stored in the Test Resources module in OpenText Application Quality Management.Likewise, you can set the default activity repository location for your custom API test activities in the Test Resources module.
Take advantage of all the features provided with the Resources and Dependencies model.	For details, see Using resources and dependencies.
Use the QCUtil object to access and use the full functionality of the ALM OTA (Open Test Architecture) (GUI testing only)	This enables you to automate integration operations during a run session, such as reporting a defect directly to an ALM database. For details, see the Utility Objects section of the Object Model Reference and the ALM Open Test Architecture documentation.
Use the TDOTA object in your automation scripts to access the ALM OTA (GUI testing only)	For details, see the Object Model Reference or the Automation Object Model Reference.