Upgrade documents from previous versions

If you have documents created in previous versions of UFT, you can upgrade them for OpenText Functional Testing.

API Test Batch Upgrader Command Line Options

The following table describes the command line options:

UI Element

Description
/ALM

Indicates that ALM Connection information will follow.
/log

Indicates that the log will be written to an alternative file. By default, log files are store in the <Installdir>\bin\logs folder.
/login

Indicates that login information will follow.
/report

Instructs the upgrader tool to generate a summary report.
destination

  • For tests on the File system: The full UNC path of the folder in which to store the tests after the upgrade.

  • For tests in OpenText Application Quality Management: a target folder path under the Test Plan module, in which to store the upgraded tests.

Note:

  • The destination value must be a local or remote folder with the same write access permissions as the source path.

  • The destination folder should be an empty folder that does not include any tests.

  • If you do not specify a destination folder, the tests will be upgraded in the source folder, overwriting the originals.
domain

The name of an ALM domain in which the source tests are stored.
logfile

The full path of the file to which the log will be written.
project

The name of an ALM project in which the source tests are stored.
reportfile

The full path of an existing folder, with the file name including an extension, to where the summary report should be written. For example, c:\logs\MySummary.txt.

source

  • For tests on the File system: The full UNC path of the folder containing the tests to be upgraded.

  • For tests in OpenText Application Quality Management: a source folder path under the Test Plan module).
url

The URL of an ALM instance to which to connect in the following form: http://{instance_domain}:8080/qcbin
username, password

For ALM mode, the username and password with which to log in to the ALM project.

Back to top

Options if you were unable to upgrade

If the OpenText Functional Testing API test upgrade was unable to upgrade the test, you may need to modify the event handler code to make it compatible with the current version:

  • Change the user code file to TestUserCode.cs.

  • Change the namespace at the beginning of the file to Script.

  • Change the class definition to public class TestUserCode : TestEntities

Example:

namespace Script
{
        using System;
        using System.Xml;
        using System.Xml.Schema;
        using HP.ST.Ext.BasicActivities;
        using HP.ST.Fwk.RunTimeFWK;
        using HP.ST.Fwk.RunTimeFWK.ActivityFWK;
        using HP.ST.Fwk.RunTimeFWK.Utilities;
        using HP.ST.Fwk.RunTimeFWK.CompositeActivities;
        using System.Windows.Forms;
        using HP.ST.Ext.FTPActivities;
    
    
        [Serializable()]
        public class TestUserCode : TestEntities
        ...