background image
<< Test Cases - Preparing to record | Test Cases - Recording the setup stage >>
Test Cases - Using the Record Status window
<< Test Cases - Preparing to record | Test Cases - Recording the setup stage >>
User's Guide
5 D
Overview of recording the stages of a testcase
and so on). Testcase names are not case sensitive; they can be any length
and consist of any combination of alphabetic characters, numerals, and
underscore characters.
Select DefaultBaseState in the Application State field to have the built-in
recovery system restore the default base state before the testcase begins
executing. Select another application state if you want the recovery
system to perform an additional sequence of steps after the default base
state is restored but before the testcase begins executing. For more
information on application states, see "Using application states" on
page 185.
The application state you chose is made the default application state and
is suggested in the Record Testcase dialog the next time you record a
Note If you choose "(None)" as the application state, the
recovery system will not be used at all. This means that you must
manually put your application in the starting state before running
the testcase.
If you do not want SilkTest to display the status window it normally
shows during playback when driving the application to the specified base
state--perhaps because the status bar obscures a critical control in the
application you are testing--uncheck the Show AppState status window
check box.
Click the Start Recording pushbutton.
The following sequence of events occurs:
The Record Testcase dialog closes.
Your application is started, if it was not already running.
The editor window disappears from the display.
The Record Status window appears.
Using the Record
Status window
As you move around the application while recording, the Record Status
window dynamically updates to show the object that the recorder thinks
the mouse is currently over or the control that has focus.