Perform Tests on the AUT
GUITAR can handle two
categories of applications GUIs.
q GUI developed using native Win32 architecture
q GUI developed using Java
There are minor differences that the tester
needs to pay attention to while testing either of these types of GUIs.
In order to test the GUI
of the AUT, the tester has to perform a certain set of steps. These steps are
detailed below
q
Initialize configurations in GUITAR for the AUT
q
Rip the GUI structure of the AUT
q
Generate the event flow graphs
for the AUT from the GUI structure
q
Generate testcases for the AUT from the event flow
graph
q
Instrument the source code of the AUT to
enable coverage report generation
q
Replay the testcases on the AUT to obtain coverage
information
q
Evaluate coverage of the testcases
Initialize configurations in GUITAR for the AUT
Before the tester can perform testing activities on
an AUT, he needs to specify the following information about the AUT
q The type of
the AUT. Win32 or Java
q The location
of the AUT’s binary executable or class files
To specify this, click Preferences from the project. Figure 1 shows the project preferences window.
Fig 1. Preferences window for initializing the
application type
For Win32 Applications
q Select the Win32 Application radio button
q In the Select Proper File, click the 
to choose the location of the executable
file.
q Or type in the
proper path.
For Java Applications:
q Select the
type of files the Java Application uses, either Jar File or Class File
q Click the 
to choose the folder containing the Jar File or Class Files
q Specify the
class containing main by selecting
that class and clicking >>
q If the java
application is invoked using a Jar
file, the main class must also be specified in the space provided
q Click Ok to save the project preferences
Rip the GUI structure of the AUT
To begin testing an application, the tester first needs to determine the
GUI structure of the AUT. Running the Ripper applications on the AUT
automatically does this.
Types of rippers are available for analyzing the
AUT.
For analyzing
an AUT developed using
q Java use the JavaGUIRipper
q Native Win32 use Windows GUI Ripper
Generate the Event Flow Graph
The Event Flow Graph is generated from the GUI
structure, ripped in the above step. To learn how to use the EFGGenerator, click here.
Generate Test cases
To generate testcases from the event flow graphs use the TCGenerator
The testcases can be executed on both the instrumented and
uninstrumented code of the AUT. To execute the testcases select Execute ->
Testcases. You are now asked to confirm if the code is instrumented or
uninstrumented. (see Figure 3)
Fig 3. Testcase execution
Execute the coverage evaluator to analyze the
coverage generated when the testcases were executed on the instrumented AUT. A
coverage report is generated by the instrumented code, when the testcases are
replayed on it. The coverage evaluator analyzes this report and a summary
report is generated.
To execute the coverage evaluator,
q Select Generate -> Coverage Report for Executed
Testcases (see Figure 4)
q Select the
a.out file generated by the instrumented code.
Fig 4. Running the coverage
evaluator
GUITAR – GUI Testing Framework
Create a new project for the Application Under Test
Maintain project configurations for the
AUT