Use the following procedure to become familiar with the sample Silk Test Classic Flex application, the Component Explorer.
To record a test case for the Component Explorer:
WebBrowser.BrowserWindow.Application.CompLibTree.Open("Visual Components") WebBrowser.BrowserWindow.Application.CompLibTree.Open("Visual Components>General Controls") WebBrowser.BrowserWindow.Application.CompLibTree.Select("Visual Components>General Controls>SimpleAlert") WebBrowser.BrowserWindow.Application.Button1.Click() WebBrowser.BrowserWindow.Application.Ok.Click() WebBrowser.BrowserWindow.Application.CompLibTree.Close("Visual Components>General Controls") WebBrowser.BrowserWindow.Application.CompLibTree.Close("Visual Components")
The Silk Test Classic Flex Automation SDK is based on the Automation API for Flex. The Silk Test Classic 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 Component 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, refer to the Apache Flex Release Notes.