An
Introduction to GTT
(Author: Tung-Hung Tsai, Bing-Ying Du)
1. GTT
Main Window
There are five areas in the main window (see Figure 1) of GTT when starting successfully: Test Sequence Editing, The Events or Tests, Error Message, Description of selected node, and Abstract information of component. The Test Sequence Editing area on the left side of the main window is the most important part of our system. A test flow is executed step by step for every node of the test script from top to bottom. By using different nodes, a test flow can verify execution results, send events to AUT or reset the application. A test script consists of four kinds of nodes: composite node, event node, test node and reset node (see Table 1).
Figure
1 The GTT main window
Table
1 Description of nodes
|
Icon |
Name |
Function |
|
|
A folder (or composite node) |
Parent node of event and test nodes to simplify
complicated test sequence. |
|
|
Event node |
Save events from user’s operation to replay user’s
operation when playing. |
|
|
Test node |
Check point saving wanted result to validate the really
execution result. |
|
|
Reset node |
Reset program under test to the initial state. |
The event node 
and test node 
usually contain component information. A
component information starts with a node icon (see Figure 2) and a component icon
(corresponding to the component’s class). Next to the component icon is a list
of bracketed descriptions. The first bracketed description is the text
displayed on the component. The second one is the name of the component. The
third one is the class of the component.
Figure
2 Information of event nodes
When using an external test node to verify an execution result, the test node does not contain the component’s information (see Figure 3). Following the test node icon is an icon indicating an external test point (external test program). The next bracketed description is the class name of the external test program.
Figure
3 Information of test nodes in plug-in method
Abstract
information of selected node
area is on the left hand bottom corner of the main window. The information of
selected node is displayed in the order (see Figure 4): class, text, name, component index (#), component index name (#N), WinClass and WinName.
Figure 1 Abstract information of selected node
The Events or Test area is on the top right corner of the main window. It is used to
display the data and editable methods associated with the event or test node
selected in the test script on the left side. If an event node is selected, its action type, sleep time
and event information are shown
successively (see Figure 5).
Figure
5 Information of a input event
Not all components support all the same set of events. Neither do
they have the same information. If a test node is selected, its test method, expected return
value, error message, parameter type and parameter value which are shown (see Figure 6). If an external test
program node selected, the information shown are test class, test method
and parameter type (see Figure 7).
Figure
6 Information of Internal test point
Figure
7 Information of External test point
Description of selected node, on the right side of the main window, is used to describe each
node’s information in the test script. Test designer can select a node and then
key in the description wanted. Error
Message, below the Description of selected node, is a field to display error at run time. When a test script fails
to execute, error messages are generated. Test designer may observe the error
messages by clicking the node with errors. GTT uses color to indicate the
correctness of the execution result. Green icons 
indicate that the execution is correct
and red icons 
indicate failure. Back
2. Toolbar
Each area has its own toolbar. The main toolbar (Figure 8) provides many functions: New File, Open File, Save File, Save File As, Close File, Run, Stop, Record, Break, Open Application, Reopen Application and Configuration from left to right successive. The usages of these functions are shown in Table 2.
Figure
8 Main toolbar
Table
2 Detail of main toolbar’s function
|
Icons |
Name |
Function |
Remark |
|
|
New File |
Create an empty test script |
|
|
|
Open File |
Open an existing test script |
|
|
|
Save File |
Save the current test script |
If it is unnamed, a file management dialog will be
opened. |
|
|
Save File As |
Save the current test script to a new file. |
A file management dialog will be opened. |
|
|
Close File |
Close current test script |
|
|
|
Run |
Execute the test script |
The AUT will be reset and executed. |
|
|
Stop |
Stop recording |
Test designer needs to select the position (before,
within, or after) of the recorded event flow. |
|
|
Record |
Start recording |
It will record the interaction between test designer
and AUT until test designer stops recording. |
|
|
Break |
Set a break point |
A break point causes the test script to stop
execution temporarily. |
|
|
Open Application |
Open an AUT |
Choose (or change) the AUT associated with the
current test script. |
|
|
Reopen Application |
Reopen an AUT |
Reset and restart the AUT. |
|
|
Configuration |
Open configuration dialog |
Change the configuration of GTT and AUT. |
|
|
About |
Version information |
|
The testTreeToolBar (Figure 9), in the Test Sequence Editing area, provides functions to edit test scripts. These functions are Stop Action, Insert Event, Insert Test, Java, Add State Node, Manual Add Node, Edit, Remove, Move Up, Move Down, Cut, Copy, Paste, UnProxy, Proxy Copy, Proxy Paste, Convert, Reset Application, Reset Test Script, and Synchronize. See Table 3 for the usages of these functions.
Figure
9 Test tree toolbar
Table
3 Detail of Test Tree toolbar’s function
|
Icon |
Name |
Function |
Remark |
|
|
Stop Action |
Stop intercepting events. |
Stop the interception of event without saving. |
