Errors Pane

Relevant for: GUI tests and components, function libraries and API testing

The Errors pane lists syntax errors found in your testing documents. Double-click an error to locate its source.

To access

Select View > Errors.

Errors may have the following severity levels: Message, Warning, or Error, and include the following types.

Code syntax errors

GUI testing

UFT checks for syntax errors when switching from the Editor to Keyword view and vice versa. Check manually by selecting Design > Check Syntax.

View a description of each of the VBScript errors in the VBScript Reference.

API testing

See the Microsoft C# Reference for help resolving code errors.

Back to top

Missing resources

Missing resources may cause a run to fail, and include:

  • Missing GUI actions.

  • Missing function libraries.

  • Missing object repositories.

  • Missing recovery scenarios

  • Missing environment variable files

  • Unmapped Shared Object Repository Parameter Values

Double-click an error description to resolve the error. Navigate to the missing resource and associate it with your test.

See also:

Note:  

Missing actions are not displayed if a test is open in read-only format.

Resources located in password-protected areas are always listed as missing if they are opened after opening the test or application area.

Back to top

Missing references

Reference files located in password-protected areas are always listed as missing if they are opened after opening the test.

To locate a missing reference file:

  1. Locate the source of the missing reference files.

    The relevant test code file opens and the cursor flashes at the place in which the missing reference file is called during a test run displaying the reference file's name.

  2. In the Solution Explorer, right-click the References node located under an API test and select Add Reference.

  3. Navigate to the missing reference file and associate it with your test.

See also:

Add Reference Dialog Box

Back to top

Missing property values

For details on input properties for API test steps, see Standard Activities.

To locate a missing test step property value:

  1. Locate the source of the missing reference files.

    The field requiring the missing property value is highlighted in the Properties pane.

  2. Enter the required information for the property value.

See also: