The TestDriver tool is a testing robot targeted toward graphical Windows applications. TestDriver records mouse and keyboard actions to produce an editable script and allows capturing certain aspects of the program under test. This is a very powerful tool for testing graphical applications as the scripts can be modified to use typical programming constructs such as loops, conditions, function calls, assignment, parameters and verification.

The main styles of testing are black box, white box, and a hybrid form of both black box and white box testing (see more about these testing methodologies in "How STF Fits into Testing Methodologies" in the printed documentation). TestDriver is especially fitted to support black box testing with features that allow it to examine certain internal aspects of the program under test. For example, if you were to test Windows Notepad from strictly the black box standpoint using TestDriver, you would be able to record and play back actions such as interaction with the menu options as well as keyboard operations such as CTRL+X, and CTRL+V.

TestDriver Project grid

 Project Page

The Project View shows a list of the scripts in the project. Each script has a name, a description, and a language. The name is used to refer to the script from other scripts and must consist only of letters, digits and the underscore character. The description may contain any characters and it is not used internally by Quality Suite TestDriver. The language indicates the dialect in which the script is currently stored. The language may be changed via the Script Editor’s context menu.

TestDriver Log grids 

 Routines Page

The Logs View shows the current project’s history of execution. The panel is split into two views, the Master Log and the Detail Log.

The Master Log shows an entry for each top-level script that has been run with start and end times, the name of the script and a status indicating whether the run passed or failed and an error message in case of failure.

The Detail Log shows detail information for the currently selected entry in the master log. By default, Quality Suite TestDriver does not emit information to the Detail Log. Scripts may emit explicit messages to the detail log using the built-in Log object. See the section on built-in objects for further information on this.

 TestDriver Script Editor window

 Script Editor Window

The Script Editor panel consists of an editor and a status bar. The status bar shows the current line number and position. It also indicates with an asterisk when a script has been modified but not yet saved.

The Script Editor is a text editor for creating and modifying scripts. A script is loaded into the editor by selecting it in the list. If you have the "Use Multiple Edit Windows" option checked, the script will be opened in a new window. If you currently have the "Use Multiple Edit Windows" option disabled, Quality Suite TestDriver will reuse an existing open editor window if one exists.

Scripts are syntax-checked when you leave the editor page, so it is not possible to save projects containing invalid scripts.

Common Tool Features Page

Click the link above to see the common features across all tools.

Home | Products | Nexus Quality Suite