The Flex Automation API introduces the
automationName and
automationIndex properties. If you provide the
automationName,
Silk4J uses this value for the recorded window declaration's name. Providing a meaningful name makes it easier for
Silk4J to identify that object. As a best practice, set the value of the
automationName property for all objects that are part of the application's test.
Use the
automationIndex property to assign a unique index value to an object. For instance, if two objects share the same name, assign an index value
to distinguish between the two objects.
Note: The
Silk Test Flex Automation SDK is based on the Automation API for Flex. The
Silk Test Automation SDK supports the same components in the same manner that the Automation API for Flex supports them. For instance,
when an application is compiled with automation code and successive SWF files are loaded, a memory leak occurs and the application
runs out of memory eventually. The Flex Control Explorer sample application is affected by this issue. The workaround is to
not compile the application SWF files that Explorer loads with automation libraries. For example, compile only the Explorer
main application with automation libraries. Another alternative is to use the module loader instead of swfloader. For more
information about using the Flex Automation API, see the
Apache Flex Release Notes.