The following actions are available from the Home toolbar. The first two are only available if a Script is opened from Qualify.

• Save – The save will take place immediately.  Click the down arrow beneath the Save icon to perform the save but also close the Script Editor afterwards.  Newly recorded Scripts can only be saved from a Playlist, therefore if the Script Editor is opened from a Playlist and the Script has not yet been saved, the Save As option is disabled. 

• Save As – Display the save dialog which provides the opportunity to save a copy of the Script to a new name and/or location.  Newly recorded Scripts can only be saved from a Playlist, therefore if the Script Editor is opened from a Playlist and the Script has not yet been saved, the Save As option is disabled. 

• Close – Close the current Script, if there are any unsaved changes a warning message is displayed.

The next three options are only available if a Script is opened from a Playlist.

• Accept Changes – The Script Editor is closed and any changes made to the Script will now be available in the Playlist but will not be saved to the database until the Playlist or the Script is saved. 

• Create Copy – Create a new Script which is a copy of the one being edited, including any changes made in the Script Editor.  When the Accept Changes button is clicked, this script will be added into the Assets tree in the Playlist from where it can be used and saved.

• Cancel – The Script Editor is close and any changes made will be lost.

• Test – For Scripts to be played back and results for the execution saved, they must be incorporated into a Playlist. If however you have just recorded a new Script for example and simply wish to check that it works, click on the Test button.  If the TestDrive Sidebar is not already open then it is automatically launched, the application under test is also launched if this is specified within the application definition, following that playback will begin.  If any issues are encountered at playback time which cause playback to end then a dialog appears at the bottom left of the TestDrive Sidebar indicating the nature of the issue.  This can be used to diagnose and fix the issue.

• Options – The Options control the settings that affect the recording and playing back of events such as screens and input.  It is very likely that different settings will be required by different types of application and these can be selected here.  Another version of an Option set can also be chosen.  See later section for more information.

• History – A full audit trail of all changes that have been made to the Script.  See later section for more information.

• Animate – Watch a simulation of the Script playback.  This does not require the target application to be active as it is in effect a ‘movie’ of what will happen.  Sound can optionally be switched on to provide commentary.  See later section for full details.

• Insert New – Place the Script into Record mode.  If the TestDrive Sidebar is not already running it will be automatically launched and the Applications panel displayed.  This lists all applications currently running on the PC for which a matching Application Definition exists.  Click on one of these to begin recording all activity for that application.  When recording is stopped, you will be presented with a choice about where in the original Script new screens and input should be inserted.  See later section for more information.

• Edit – The window that is displayed depends upon which event is in focus at the time.  Either the Script, screen or input details are shown from where changes can be made.  Each of these is explained fully in a later section.

• Move Up/Move Down – Move the selected screen or input up or down in the list of events.  You will be prevented from moving an input to the top of the list as a Script must always begin with a screen.