User Guide

About operations 15
If the FlexButton object has no label, QTP uses the ToolTip of the Button for the test object
name. If there is no label and no ToolTip, QTP uses the source code’s
id property. If the Flex
developer did not specify an
id, QTP uses the index. If you omit all of these, QTP uses its
own numbering scheme to identify the object.
The ordering of properties to determine the test object name varies depending on the object.
Other objects whose test object names are not the same as the Flex
id properties, include
FlexAccordionHeader, FlexButtonBarButton, FlexCheckBox, FlexLink, FlexPopUpButton,
FlexRadioButton, FlexScrollThumb, FlexSimpleButton, FlexSliderThumb, and FlexTab.
About operations
When you interact with a Flex application while recording, your actions are stored in the
QTP script. These actions, such as the click on a button, define the narrative of the test script.
They are known in QTP as operations. In Flex, they are known as events. Each operation
defines an interaction with a control in the Flex application. You generally use a combination
of operations to perform complex interactions with Flex applications, such as filling out a
form and submitting it or dragging several objects and dropping them in a particular location.
Flex controls such as button define many events. These events include common ones like
click, showToolTip, and focusIn, but also events that are rarely or never invoked directly by
the user, such as creationComplete, render, and invalid. Flex events also include very granular
actions such as mouseMove, keyDown, and focusOut.
The most commonly-used Flex events are available for use in QTP as operations. However,
QTP does not record all events. QTP records the semantically important gestures, or
operations that are logically atomic. That is, recording a click event, rather than the
combination of the mouseDown and mouseUp events; or recording a ComboBox’s select
event, rather than a mouseDown, open, drag, mouseUp, and close event sequence.
When creating a test, not all events that can be recorded are recorded. For example, the
mouseMove event for most controls is not recorded by default. If it were, the script would
include a new step for every mouse movement, which would quickly overwhelm the test. You
can instruct QTP to play back this event by adding it manually to the test script. To see a list
of available operations for each Flex component, see the QTP Object Type Information
document.
In some cases, QTP plays back some of these events as a sequence of smaller events. Click, for
example, is played back as a mouseDown and mouseUp event pair, or keyDown and keyUp,
depending on how it was invoked.