DefaultBaseState Function

Silk Test Classic provides a DefaultBaseState for applications, which ensures the following conditions are met before recording and executing a test case:

The application is running.
The application is not minimized.
The application is the active application.
No windows other than the application’s main window are open. If the UI of the application is localized, you need to replace the strings, which are used to close a window, with the localized strings. The preferred way to replace these buttons is with the lsCloseWindowButtons variable in the object’s declaration. You can also replace the strings in the Close tab of the Agent Options dialog box.

For Web applications that use the Open Agent, the DefaultBaseState also ensures the following for browsers, in addition to the general conditions listed above:

The browser is running.
Only one browser tab is open, if the browser supports tabs and the frame file does not specify otherwise.
The active tab is navigated to the URL that is specified in the frame file.

For web applications that use the Classic Agent, the DefaultBaseState also ensures the following for browsers, in addition to the general conditions listed above:

The browser is ready.
Constants are set.
The browser has toolbars, location and status bar are displayed.
Only one tab is opened, if the browser supports tabs.

DefaultBaseState Types

Silk Test Classic includes two slightly different base state types depending on whether you use the Open Agent and dynamic object recognition or traditional hierarchical object recognition. When you use dynamic object recognition, Silk Test Classic creates a window object named wDynamicMainWindow in the base state. When you set the recovery system for a test that uses hierarchical object recognition, Silk Test Classic creates a window object called wMainWindow in the base state. Silk Test Classic uses the window object to determine which type of DefaultBaseState to execute.