This tool allows you to peek at the window structure of an application, giving information about the UI elements and their position in the hierarchy. Use this tool to find out the class of a certain window, or its parent-child relationship with other windows. Window Explorer can also display information about Accessibility objects.
Drag the target cursor over windows belonging to other applications to see information about them. If the 'Acc' tab is selected then the tree contains the accessible objects hierarchy, otherwise it contains the structure of standard windows.
click to refresh the window tree;
enables/disables the use of MS Accessibility;
keeps this window on top of other windows.
This is where you edit your test scripts. The editor will determine the script's language based on the file
extension and will highlight numbers, strings, comments and keywords. When you click the Go button or
press F5 the script in the active code window will get executed. The editor will also display
or
if an enabled/disabled breakpoint
is set on the current line, and
on the line where the script was interrupted.
Here are some useful keyboard shortcuts:

The list of breakpoints currently set can be seen in the breakpoints window. Double-clicking a breakpoint will open the relevant source file. Setting/clearing the checkbox will enable/disable the breakpoint. Pressing DEL will remove the selected breakpoint.

When the script is stopped at a breakpoint it displays the hierarchy of calls from the script entry point up to the current function. Double-clicking on a different level in the call stack will reveal the local variables in the calling function and will recalculate the values in the Watch window in the new context.

When the script is stopped at a breakpoint it displays a list of local variables (in the current function context). To change the context to one of the calling functions double click on the relevant level in the Call Stack window. Pressing ENTER or F2, or double clicking a variable will allow editing its value. Editing must be done with caution because the script syntax allows changing the type of a variable by setting its value.

Allows evaluating expressions in the current execution context, as set from the Call Stack window. The expression can be any script expression or statement valid in the current language.

This window will display error and informational messages coming from the framework or logged from the script via Env.LogInfo, LogError or LogWarning. Along with each message there will be a link to the source file and line that was executing when the message was reported. Clicking this link will display the relevant source file.

Displays the list of script execution threads, their current state and their location.
