When the user records a new test in
Silk4J for a Flex application, the following events occur:
Silk4J calls the
Silk Test Agent to start recording. The Agent forwards this command to the FlexTechDomain instance.
- FlexTechDomain notifies AutomationManager to start recording by calling
beginRecording(). The AutomationManager adds a listener for the AutomationRecordEvent.RECORD event from the SystemManager.
- The user interacts with the application. For example, suppose the user clicks a Button control.
ButtonDelegate.clickEventHandler() method dispatches an AutomationRecordEvent event with the click event and Button instance as properties.
- The AutomationManager record event handler determines which properties of the click event to store based on the XML environment
information. It converts the values into proper type or format. It dispatches the record event.
- The FlexTechDomain event handler receives the event. It calls the
AutomationManager.createID() method to create the AutomationID object of the button. This object provides a structure for object identification. The AutomationID
structure is an array of AutomationIDParts. An AutomationIDPart is created by using IAutomationObject. (The UIComponent.id,
automationName, automationValue, childIndex, and label properties of the Button control are read and stored in the object.
The label property is used because the XML information specifies that this property can be used for identification for the
- FlexTechDomain uses the
AutomationManager.getParent() method to get the logical parent of Button. The AutomationIDPart objects of parent controls are collected at each level up
to the application level.
- All the AutomationIDParts are included as part of the AutomationID object.
- The FlexTechDomain sends the information in a call to
- When the user stops recording, the
FlexTechDomain.endRecording() method is called.