Testing the Ability of the Recovery System to Close the Dialog Boxes of Your Application

Before you begin to design and record test cases, make sure that the built-in recovery system can close representative dialog boxes of your application. Although the recovery system is robust enough to be able to close almost any application window, some applications may have windows that close in an unconventional fashion.

Here are the three types of dialog boxes you should test:

A modal dialog box, which is a dialog box that locks you out of the rest of your application until you dismiss it.
A non-modal dialog box.
A non-modal dialog box that causes the display of a confirmation dialog box.

To test the ability of the recovery system to close your the dialog boxes of your application:

Start Silk Test Classic.
If you have not already done so, record a test frame for your application.
Choose Options > Runtime to ensure that your application’s test frame file is listed in the Use Files field in the Runtime Options dialog box.
Start your application and invoke a representative dialog box.
In Silk Test Classic, click Run > Application State.
On the Run Application State dialog box, select the DefaultBaseState application state and click Run.
Silk Test Classic executes the DefaultBaseState routine, which should close the dialog box and any open windows, then display a results file. If the built-in recovery system cannot close one of the three representative dialog boxes, you need to modify the recovery system so that it understands how to close the dialog box.