When you extend Flex components that are already instrumented, you do not have to change anything to ensure that those components' events can be recorded by a testing tool. For example, if you extend a Button class, the class still dispatches the automation events when the Button is clicked, unless you override the Button control's default event dispatching behavior.

Automation events (sometimes known in automation tools such as QTP as operations) are not the same as Flex events. Flex must dispatch an automation event as a separate action. Flex dispatches them at the same time as Flex events, and uses the same event classes, but you must decide whether to make a Flex event visible to the automation tool.

Not all events on a control are instrumented. You can instrument additional events by using the instructions in Instrumenting existing events.

If you change the instrumentation of a component, you must edit that component's entry in the TEAFlex.xml file. This is described in Using the class definitions file.