Share this page

# Test Resources

The Test Resources module enables you to manage resources used by your tests.

In this topic:

## Test resources overview

You can organize your resources by defining a hierarchical test resource tree containing resource folders and resources.

For each resource in the tree, you select and upload a set of resource files to the repository. These files can be used by one or more tests. You can then define dependencies between resources and tests.

- Business Process Testing: When a project with Business Process Testing is connected to OpenText Functional Testing, a BPT Resources folder is created automatically in the tree. The BPT Resources folder contains all the OpenText Functional Testing resources available for business components in the project. For details about Business Process Testing application areas, see Business components overview.

- Sprinter: When Sprinter is used for manual testing in your project, a Sprinter folder is added to the Resources folder. This folder contains a subfolder for each Sprinter user and is used to store user information.

  Caution: The Sprinter folder is managed by Sprinter only. You must not make any changes to the folder or subfolders.

Example: Michael, a QA tester, works with an external testing tool that stores its tests in OpenText Application Quality Management. Each test uses a shared configuration file that is common to a number of tests. He therefore wants a single point of maintenance for the configuration file, rather than saving separate copies of the file for each test.

Michael uses his testing tool to define the configuration file as a resource and define each test that uses the file as dependent on that resource. As only one copy of the resource exists, replacing the configuration file would replace it for all tests that depend on it.

After Michael defines dependencies, if he attempts to delete the resource, Michael is warned that this may affect tests that depend on it. In addition, if Michael copies one of the tests that depend on the resource between projects, he can choose to copy the resource as well as the test.

Back to top

## Manage test resources

Create a test resource tree, upload and download resources, and define dependencies between resources and other entities, such as tests.

If you are working with OpenText Functional Testing resources, see the section on working with OpenText Application Quality Management in the OpenText Functional Testing help.

To manage test resources:

1. Create a resource folder.

   Right-click the Resources root folder and select New Resource Folder. To create a sub-folder, right-click a folder and select New Resource Folder.

2. Add resources to a folder.

   Right-click a folder or sub-folder and select New Resource. Fill in the fields in the New Resource dialog box, and click OK.

   UI Element | Description
   --- | ---
   Name | The name of the resource.
   Type | Indicates the type of resource. The default value is Test Resource. Available types include: Analysis Template. Contains templates for performance test analysis reports. For details about analysis templates, see the OpenText Enterprise Performance Engineering help. API Test Shared Resources. Contains imported services for use in OpenText Application Quality Management with: API tests, which are created in OpenText Functional Testing Business process tests or flows that contain business components that are automated for API testing For details about sharing services, see the information about activity sharing in the OpenText Functional Testing help. Application area. Provides all settings and resources required to create the content of: OpenText Functional Testing GUI tests Business process tests or flows that contain business components with automated GUI facets Data Table. Contains data to be used for driving run steps for: Test configurations OpenText Functional Testing GUI tests and API tests Environment Variables. Contains variables and corresponding values that can be accessed from: OpenText Functional Testing GUI tests Business process tests or flows that contain business components with automated GUI facets Function Library. Contains Visual Basic script functions, subroutines, and modules for use with: OpenText Functional Testing GUI tests Business process tests or flows that contain business components with automated GUI facets Monitor Over Firewall. Contains LoadRunner Enterprise monitor settings for servers that are located over a firewall. For details about monitor over firewall, see the LoadRunner Enterprise help. Monitor Profile. Contains LoadRunner Enterprise monitor settings that can be saved as a monitor profile to be used by any load test in your project. For details about monitor profiles, see the LoadRunner Enterprise help. Recovery Scenario. Contains scenarios which include definitions of unexpected events and the operations necessary to recover OpenText Functional Testing run sessions. Shared Object Repository. Contains information that enables OpenText Functional Testing to identify the objects in your application. You can maintain the reusability of your tests by storing all the information regarding your test objects in shared object repositories. For details about shared object repositories, see the OpenText Functional Testing help. Test Resource. A generic test resource type for use by all test types. Testing Activity.

3. Upload resource files.

   In the Resource Viewer tab of the resource, click Upload File. It includes the following options:

   - Upload File. Opens the Upload File dialog box, enabling you to select a file.

   - Upload Folder. Opens the Browse for Folder dialog box, enabling you to select a folder.

   To replace an uploaded file or folder, upload again.

   To view the resource content, you must install the relevant add-in or extension.

   Business Process Testing:

   When working with application areas, launch the testing tool in the Application Area Viewer tab to work with the resource.

   The Launch button is disabled when attempting to open an application area from an older version or baseline. Instead, open the application area directly in QuickTest Professional.

4. To view and edit your test resources, you can download them to a local directory.

   Select a resource in the test resource tree and click the Resource Viewer tab. Click Download and specify the local directory where the resource is downloaded.

5. Define dependencies between test resources and other entities.

   You define dependencies between resources and tests from your testing tool, for example, OpenText Functional Testing. For details, see the UFT One help.

   You can also define dependencies between entities by writing your own application. For details, see Open Test Architecture API Reference.

6. To view dependencies between a test resource and other entities, select the test resource, and click the Dependencies tab.

   To view which entities depend on the selected test resource, check the Used by table.

   To view which entities the selected test resource depends on, check the Using table. If a related entity no longer exists, it is marked as a broken relation . You can click Show Broken Relation to view the details of the broken relation.

Back to top

## Copy test resources

You can copy test resources across projects.

To copy a test resource:

1. In the Testing > Test Resources tree, select the resource or folder that you want to copy. To copy more than one item, use the CTRL key.

2. Select Edit > Copy. Alternatively, right-click and select Copy.

3. Log in to the project to which you want to paste the resource or folders, and navigate to the Testing > Test Resources tree.

4. Select the folder to which you want to copy the resources or folders.

5. Select Edit > Paste. Alternatively, right-click and choose Paste. Select one of the following options:

   Option | Description
   --- | ---
   Copy resources and link to existing related entities | Copies the test resources and pastes them into the target project. The copied test resources are linked to existing entities with the same name and path. If a related entity does not exist in the target project, it is copied to the target project.
   Copy resources and related entities | Copies the test resources along with the related entities, and pastes them into the target project. If an entity already exists in the target project, the copied related entity is renamed to resolve the duplicate name.
   Copy resources without copying related entities | Copies the test resources without copying the related entities, and pastes them into the target project. The copied items are not linked to any related entities.

Back to top

See also:

- Application area

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: