A test frame is an include file (.inc) that serves as a central global repository of information about the application under test. It contains all the data structures that support your test cases and test scripts. Though you do not have to create a test frame, by declaring all the objects in your application, you will find it much easier to understand, modify, and interpret the results of your tests.
When you create a test frame, Silk Test Classic automatically adds the frame file to the Use files field of the Runtime Options dialog box. This allows Silk Test Classic to use the information in the declarations and recognize the objects in your application when you record and run test cases.
When you enable extensions, Silk Test Classic adds an include file based on the technology or browser type that you enable to the Use files location in the Runtime Options dialog box. For extensions that use the Open Agent, Silk Test Classic names the include file <technology_type>.inc. For instance, if you enable extensions for an Apache Flex application, a file named flex.inc is added. If you enable extensions for an Internet Explorer browser, Silk Test Classic adds the explorer.inc file to the Runtime Options dialog box.
A constant called wStartup is created when you record the test frame. By assigning the identifier of the login window to wStartup and by recording a new invoke method, your tests can start the application, enter any required information into the login window, then dismiss the login window.
See Marking 4Test Code as GUI-Specific to learn about the ways you modify the test frame when porting your test cases to other GUIs.