Known issues - Opening documents

Relevant for: GUI tests and components and API testing

This topic describes general troubleshooting and limitations for creating, opening and saving testing documents.

Hidden files

OpenText Functional Testing does not support hidden files. If you mark an OpenText Functional Testing test, or other OpenText Functional Testing file as hidden (by selecting the Hidden attribute), OpenText Functional Testing may behave unexpectedly.

Back to top

Documents last saved in earlier versions

Last saved in QuickTest 9.5

Document opens in read-only mode.

Open the document in QuickTest 10.00 or 11.00 to upgrade it.

Last saved in a QuickTest version earlier than 9.5

An error is displayed in the Error pane, and the document is not opened.

Open the document in QuickTest 10.00 or 11.00 to upgrade it.

Last saved in QuickTest 10.00 or later Can be opened and modified directly in OpenText Functional Testing.

When upgrading a document:

  • Relevant add-ins must be installed.

  • Tests saved in the upgraded format can no longer be used with previous versions of QuickTest.

Tip: If you have many tests to upgrade, create a script that iterates through all your tests to open and save each one in the new format. For more details, see Product automation scripts.

Back to top

Opening and saving tests with resources

When you save a test together with its resources, OpenText Functional Testing also saves any tests containing external actions.

However, these called tests contain only the specific actions called from your test, and not all the actions in the called test. These called tests cannot be opened from the local copy.

If you need full access to all called tests, as well as your main test, save all tests locally, and then manually edit all references to the relevant actions from the main test.

You cannot save a test with resources when the test calls an external action which, in turn, calls another external action.

Back to top

Windows Libraries

The Windows Libraries feature is not supported. If you attempt to open a test from a library location or save a test to a library location, OpenText Functional Testing may behave unexpectedly.

Browse to your saved tests using standard file paths, even if they are included in a library.

Back to top

User Account Control (UAC)

If you open a test from a protected location (such as Program Files) and UAC is enabled, the test is opened in read-only mode.

To modify the test, copy it to another location and open the files from there.

Back to top

Renaming OpenText Functional Testing documents in ALM

Renaming an OpenText Functional Testing test or component from ALM may cause the test or component to behave unexpectedly.

Workaround: To rename a test or component, open it in OpenText Functional Testing and rename it using the Save As option. If the test or component has already been renamed from ALM, use the rename option again to restore the old name, and then use the Save As option in OpenText Functional Testing.

Back to top

Opening API tests saved in a network location

OpenText Functional Testing cannot access an API test saved on your network using a UNC address. Instead, map the network location to a drive on your computer, and access the file on that drive.

Example: To open an API test from \\10.65.0.8\APITests, map \\10.65.0.8\APITests to a network drive, for example, H. Then open the test from H:\\10.65.0.8\APITests.

Back to top

Opening tests associated with discontinued add-ins

If you open a test that is associated with an add-in that is not installed, you encounter a warning message:

"The following add-ins are associated with an open test or component but they were not installed with the UFT One"

If the add-in is available, you can install it and reopen the test.

If the add-in is no longer supported, we recommend that in the test settings you remove the add-in from the list of associated add-ins, to avoid further warnings.

Add-ins that are no longer supported: 

Add-in Status
Web services

Not supported. Use OpenText Functional Testing's API testing solution for web service testing purposes. For details, see API test design.

Silverlight

Following the discontinuance of the Silverlight development framework, OpenText Functional Testing no longer supports the Silverlight Add-in by default.

If you require the Silverlight Add-in, contact OpenText Support. For documentation, see the Help Center for version 24.2.

Flex

Following the retirement of the Adobe Flash Player, OpenText Functional Testing no longer supports the Flex Add-in by default.

If you require the Flex Add-in, contact OpenText Support. For documentation, see the Help Center for version 24.2.

Back to top