Optionally, you can use an absolute or relative path to reference header files and project header files.
For example, if you want a script to reference the header file MyHeader.sbh, regardless of the current SQABasic path, and the script and header file are in the default locations of the same project, you can use the following declaration:
The following table summarizes the differences between library files:
.sbl .rec .dll Location SQABasic path Datastore (folder TMS_Scripts) in the current project TMS_Scriptsdll folder, or a user assigned location Scope When in the SQABasic path, available to files in the same project or other projects Available to files in the same project Depends on location VP No Support Support all standard robot VP Supports Custom VP
Object-Oriented Recording – Examines objects in the AUT at the Windows layer during recording and playback. Robot uses internal object names to identify objects. If objects in your application's graphical user interface (GUI) change locations, your tests still pass because the scripts are not location dependent.
Low-level recording – Tracks detailed mouse movements and keyboard actions by screen coordinates and exact timing. Use low-level recording when you are testing functionality that requires the tracking of detailed mouse actions, such as in painting, drawing, or CAD applications.
During playback, the PlayJrnl command invokes the low-level file. This file plays back all recorded actions in real time, exactly as recorded. This differs from Object-Oriented Recording, which examines Windows objects in the application-under-test, and does not depend on precise timing or screen coordinates.
When you switch to low-level recording, Robot does the following:
Records low-level actions in a binary script file that cannot be edited.
Gives the low-level script file the next consecutive number, and displays the number in the Asset (left) pane.
Adds a PlayJrnl command to your script that references the low-level script file.
If filename references an application, SQAShellExecute runs the application.
If filename references a file other than an application executable, SQAShellExecute opens the file through the application that has a Windows association with the file type. (Windows maintains associations between an application and its file types by associating the application with a particular file extension.) For example, suppose Microsoft Word has a Windows association with .DOC files. If filename references MEMO.DOC, SQAShellExecute runs Word and opens MEMO.DOC in the Word environment.
x = SQAGetPropertyArray("Type=ComboListBox;Label=Font style:","List",a)
For i = Lbound(a) to Ubound(a)
GUI Playback Options - Trap tab Tool -> GUI Playback Options -> Trap Use to specify what information the Trap utility captures about general protection faults that occur during playback and the recovery method to use.
To include the contents of the stack for non-current tasks, select Stack trace.
To include the module and class list information, select Module and class list.
Click one of the following to specify what Trap should do after detecting a GPF:
Restart windows session – Trap restarts Windows.
Call user-defined sub procedure – Trap calls the sub-procedure in the module that you specify. Select this option to specify your own custom SQABasic error handling. Type the names of the library source file (with an .sbl extension) and the sub-procedure.
Robot uses the Trap utility to detect the occurrence of General Protection Faults (GPF) and the location of the offending function call. If a GPF is detected, Robot updates a log file that provides information about the state of the Windows session that was running.
The occurrence of a GPF usually results in a crash of the running application and may also result in a loss of data.
Capture information about GPFs.
Write the state of your environment to a log file when a GPF is detected.
Specify the type of information to write to the log file.
Automatically restart Windows or call your own error handling sub-procedure before performing any other action.
Use to verify whether a specified module is loaded into a specified context (process), or is loaded anywhere in memory.
In the Windows environment, modules are defined as executable programs (.exe), dynamic link libraries (.dll or other extension), device drivers (.sys or .drv), or display fonts (.fon).
Each process has its own context, which includes a set of loaded modules. When you create this verification point, you select the name of the module. You may also select the name of a context (process), in which case the verification point tests whether the module is loaded into that process. If no context is specified, the verification point tests whether the module is loaded anywhere in memory.
Show Hidden: Shows all objects on the Windows desktop.
Objects with a Visible property of False. Examples are hidden Visual Basic Data controls and PowerBuilder DataWindows.
Objects with no GUI component. Examples are PowerBuilder DataStore controls and Oracle Forms blocks.
When you select an object in the list, inverts the object's colors in the application window if the object is visible.
Skip VP & Acknowledge Results Select Acknowledge results to have Robot display a pass/fail result message for each verification point. You must click OK before playback continues. If selected, Robot skips verification points during playback. You may want to skip verification points for debugging during the test development phase, but not for actual testing.
Unexpected Active Window Use to specify how Robot responds to the appearance of an unexpected active window during playback. An unexpected active window is any window that is not expected by Robot during playback and that prevents the expected window from being made active.
GUI Record Options Type the default prefix for every new GUI script that you record. Each time you record a new GUI script, the prefix is appended with a consecutive number. Records a mouse drag as a mouse click within a push button, option button, check box, and label while recording. This prevents inadvertent mouse drags from being written in the script as drags.
Manage Queries Dialog Box Use this dialog box to manage script or session queries. To open: Click Tools -> Manage Script Queries . Click the New or Edit button in the Manage Queries dialog box.
To "talk" to another application and send it data, open a connection (called a DDE channel) using the statement DDEInitiate.
DDEInitiate requires two arguments:
The DDE application name. For example, the DDE name for Microsoft Word is WINWORD.
The topic name. This name is usually a open filename. Many applications that support DDE recognize a topic named System, which is always available and can be used to find out which other topics are available.
Note: The application must already be running before you can open a DDE channel. To start an application, use the Shell command.
After you open a channel to an application, you can get text and numbers (DDERequest), send text and numbers (DDEPoke), or send commands (DDEExecute). See the application's documentation for a list of supported DDE commands.
To make sure the application performs a DDE task as expected, use DDEAppReturnCode. If an error does occur, your program can notify the user.
Systems: A list of all items in the System topic
Topics: A list of available topics
Formats: A list of all the Clipboard formats supported
When you're finished communicating with the application, you should close the DDE channel using DDETerminate. Because you have a limited number of channels available at once (depending on the operating system in use and the amount of memory you have available), it's a good idea to close a channel as soon as you finish using it.