Ripper for Java apps
Replay tool
The GUIRipper analyzes a Windows based application and understands its GUI structure. We call this Windows application, which the tester is trying to analyze, the Application Under Test , hence forth called the AUT. The GUIRipper generates the integration tree for the AUT. The integration tree shows the relationship between the different components of the AUT’s GUI. The integration tree is required in the succeeding phases of testing the AUT.
As an example, fig 1 shows the integration tree generated after analyzing the WordPad application.
Fig 1 Integration tree for the WordPad application.
Usually applications have only one top-level application window. The integration tree for such applications have a single root node. However, some applications may have more than one top-level window. These applications have one root node corresponding to each top-level window. A link between a parent GUI window and a child GUI window exists if some component, such as a button or a menu item, in the parent window invokes the child dialog window. In the above example, the File->Open menu item invokes the Open dialog window.
We shall now see how to go about ripping an application. We shall use WordPad as our example.
Rip an application
This section describes how to analyze the GUI structure of a Windows AUT.
1 From the GUITAR interface select Generate -> GUI Structure
Fig 2 Launching the GUI Ripper from the GUITAR interface
This launches the GUIRipper application. Fig 2 shows how to launch the GUI Ripper. You will use GUIRipper to rip the AUT’s GUI structure. GUIRipper also allows you to edit the GUI structure of the AUT so that you can fine tune the testcase generation and execution.
2 Launch the AUT by clicking on the AUT’s program icon or from Windows explorer. Minimize or close all unnecessary windows to reduce the clutter on your desktop.
3. To analyze the AUT click the 
button.
4. Now you need to identify to GUIRipper the windows of the AUT. This is because some AUTs may have more than one top-level window. You have to do this by clicking on the Title Bar of the AUT’s top-level window. Don’t click any window that does not belong to the AUT. For WordPad, there is only one top-level window. Click it. The selected windows are recorded as shown fig 3.
Fig 3 The GUIRipper about to analyze the WordPad application.
5. Click on the title bar of GUIRipper to indicate that you have finished identifying the top-level windows of the AUT.
6. GUIRipper is now ready to analyze the AUT. Click Analyze AUT. You have to wait a few seconds while GUIRipper searches WordPad and identifies all its GUI Components.
When GUIRipper has finished analyzing the AUTs GUI structure, it will displayed for editing as shown in fig 4.
Fig 4 The integration tree for WordPad
This is the integration tree for the AUT, WordPad. It shows the relation of different GUI windows of WordPad and how they can be invoked from the top-level window of WordPad. A link from one window to another indicates that some button or menu item in the first window is used to activate the other window.
Edit the
ripped structure
GUIRipper allows the user
to edit the GUI structure as analyzed by it. To view the detailed properties of
a GUI window, double click on the 
icon for that
window. A dialog box containing the
properties of that window appears. Fig 5 shows such a property dialog
box for WordPad’s main window.
Fig 5 Propery dialog box for editing properties of a GUI windows
You can Edit the properties of that window and its components by making changes in this dialog box.
Please note that GUIRipper cannot differentiate between modal and modeless windows. The tester needs to identify modeless windows. He can do this by un-checking the <Modal> check box in the property dialog for that window.
Link GUI
windows
It is sometimes possible for
GUIRipper to incorrectly infer the relation between one window and another, in the
integration tree. For example, the 
button of the File->Page Setup->Page Setup dialog
invokes the printer setup dialog. It
may so happen that GUIRipper is unable to determine this.
The tester has the capability to manually describe the link between two such
dialog windows.
1 Right click the source/ parent dialog.
2 Drag the mouse to the target or child window and release it.
3 Select from the list, the button in the source window that activates the target window.
4 The link between the source and target window is installed.
Save the
Ripped GUI integration tree
1 Select File-> Save or click the Save icon on the toolbar. The structure is saved in the projects folder you had selected from the main GUITAR interface.
Exit GUIRipper
1 Select File-> Return to return to the GUITAR interface.