Suppressing UFT One Native Recording

When a user performs operations on the application and the Testing Agent reports the corresponding steps to record, it must also instruct UFT One not to record extraneous steps for other events that UFT One detects on the application. If this native recording is not suppressed, redundant steps are added to the test.

The Testing Agent must enable UFT One to identify the events that it must ignore and not record. This can be done in one or both of the following ways:

  • Static suppression. The testing environment XML specifies objects on which UFT One should ignore events. For more information, see the Testing Environment Schema. The static suppression definitions remain in effect as long as UFT One is open and do not change during run-time.

    In the testing environment XML, you can specify two types of objects on which to ignore events:

    • ActiveX (define a list of the ProgIDs of the ActiveX controls to ignore)

    • Standard Windows (define a list of window class names of the windows to ignore)

  • Dynamic suppression. During the recording process, the Testing Agent specifies objects on which to ignore events. To do this, the Testing Agent calls the Suppress and UnSuppress methods in the IRecordSuppressor interface. In the Suppress and UnSuppress methods, the Testing Agent provides the environment ID and a list of processes and windows on which to ignore events. The list can contain process IDs of applications and window handles. If events on a specific window are ignored, the events on windows it contains are ignored as well.

    Calling the dynamic suppression methods does not affect the static suppression defined in the testing environment XML.

    Implement the Testing Agent to call the Suppress and UnSuppress methods to update the list when a UFT One recording session begins and when processes or windows are created or destroyed.