Modifying Actions Prior to Conversion

As you add actions to the Action Conversion Tool, they are analyzed to determine if they are suitable for conversion. If an action is not suitable for conversion, the Action Conversion Tool displays a status message (in the Status column of the Action Conversion Tool window and in the log files) that describes why the action is not suitable for conversion. (If an action is suitable for conversion, no status message is displayed.)

The following table suggests solutions for status messages that may be displayed for an action. After you make your changes, save the test and re-add the action to the Action Conversion Tool.


Status Message	Solution
The action is not reusable.	Only reusable actions can be converted to scripted components. To make the action reusable: Right-click the action name and select Action Properties from the context menu. The Action Properties dialog box opens. In the General tab, select the Reusable action check box.
The action is calling another action.	Nested actions are not supported for components. Modify the action so that it does not contain calls to nested actions.
The action contains a parameter of type "Any".	The parameter value type, Any (defined in the Parameters tab of the Action Properties dialog box), is not supported for components. Select another value type for the action parameter or remove the parameter from the action.
The action uses a parameter in a global data sheet.	If the action uses a parameterized checkpoint, the value must be stored in a local data sheet. To modify the checkpoint to use a local (current action) data sheet: Open the Checkpoint Properties dialog box for the parameterized checkpoint and click the Parameter Options button. The Parameter Options dialog box opens. Select the Current action sheet (local) radio button and click OK. The data sheet column from the global data sheet is automatically copied to the local data sheet. Note that only the data in the first row is used by the scripted component. Click OK to close the Checkpoint Properties dialog box.
The action's script. refers to global data sheet.	Components cannot use global data sheets. (Information cannot be passed between actions.) Modify the test so that it uses a local (per-action) data sheet (and not a global data sheet).
The action uses a shared object repository that is not saved in Quality Center.	Components can use only shared object repository files that are stored in the Quality Center project. Save the shared object repository as an attachment in the Test Plan module of your Quality Center project (for example, Subject/BPT Resources/Object Repositories). Then, in the source test, associate the file with the action using the Associate Repositories dialog box (Resources > Object Repository > Tools > Associate Repositories). After you convert the action to a scripted component, you need to associate the component with the application area that provides access to this shared object repository. For more information, see Converting Actions to Scripted Components.
The source test uses a function library that is not saved in Quality Center.	Components can use only function library files that are stored in the Quality Center project. Save the function library file as an attachment in the Test Plan module of your Quality Center project (for example, Subject/BPT Resources/Libraries). Then, in the source test, associate the file with the test (using the Test Settings dialog box). After you convert the action to a scripted component, you need to associate the component with the application area that provides access to this function library. For more information, see Converting Actions to Scripted Components.
The source test uses an environment file that is not saved in Quality Center.	Components can use only environment files that are stored in the Quality Center project. Save the environment file (as an attachment in .xml format) to Subject/ in the Test Plan module of your Quality Center project. Then, in the source test, associate the file with the test (using the Test Settings dialog box).
The source test uses a recovery scenario file that is not saved in Quality Center.	Components can use only recovery scenario files that are stored in the Quality Center project. Save the recovery scenario file(s) in the Test Plan module of your Quality Center project (for example, Subject/BPT Resources/Recovery Scenarios). Then, in the source test, associate the file with the test (using the Test Settings dialog box). After you convert the action to a scripted component, you need to associate the component with the application area that provides access to this recovery scenario file. For more information, see Converting Actions to Scripted Components.
The source test uses a Data Table that is not saved in Quality Center.	Components can use only external Data Tables that are stored in the Quality Center project. Save the external Data Table (as an attachment in .xls format) in the Test Plan module of your Quality Center project (for example, Subject/BPT Resources/Recovery Scenarios). Then, in the source test, associate the file with the test (using the Test Settings dialog box).
This test was created using an earlier version of QuickTest.	The Action Conversion Tool can only convert actions from tests created using the current version of QuickTest. Before you can convert an action from this test, you must open and save the test using the current version of QuickTest. This upgrades the test to the current version of QuickTest. Alternatively, if you do not want to upgrade the test to the current version, you can use an earlier version of the Action Conversion Tool (installed with an earlier version of QuickTest).

Note: The Action Conversion Tool may not recognize that an action refers to the global data sheet in the following cases:

If the global data sheet was renamed to something other than Global.

If the action previously contained at least one local parameter, which was changed to a global parameter (whose value is stored in the global data sheet).

In these cases, the Action Conversion Tool may convert the action, but when the scripted component runs, it will fail. (This is because components can only access local data sheets.)