Here is the issue.
Create an API test in UFT v12.02. This test should include input and output parameters.
Create a GUI test that contains a call to this API test (created in step 1). Include data for the input parameters.
Run the GUI test successful.
Open the API test and add an additional input parameter.
Open the GUI test, and add some data for that additional parameter in the API call.
Run the GUI test. You will receive an error. Please let me know if you do not.
The fix was to remove the call to the API test, and then to reinsert the call.
I would like to know if this is a known issue. It will cause some maintenance concerns we need to account for.
Answer by bubblehead712 · Dec 13, 2016 at 06:47 PM
I am sorry to say this behavior is not a bug but is describe as follows in the UFT Object Model Reference > Utility Objects > Utility Statements > RunAPITest statement.
- The *RunAction* statement can run only actions that are already associated with your test as part of the test flow. Therefore, in order to enter a *RunAction* statement in the Editor for an external action, you must first insert a call to the action (Design > Call to New Action) or copy the external action (*Design > Call to Copy of Action*) into your test. Using this option associates the action with the test and also inserts a *RunAction* statement for you. After the external action is added to the test flow, you can add additional calls to that external action in the Editor. - If you insert a *RunAction* statement in the Editor for an external action that is not already associated with your test as a part of the test flow, the *RunAction* statement fails. For more details on copying or calling external actions, see the *HP Unified Functional Testing User Guide*. - Do not use this statement to call an external action from within a function library. Instead, use the *LoadAndRunAction* Statement. - This statement is not supported in the Console Pane (Debug panes).