This
section describes the process of creating functional test scripts to test
your applications.
Recording a script
To start recording scripts against
your applications, you must first configure your test environments, configure
your applications, and create a project.
Starting your test applications
When recording tests on your application,
it is best to have Functional Tester start the application during recording
using a startApp command. This makes playing back the tests more reliable
because startApp uses the application configuration information. Functional
Tester will open either Java™ applications that you specify or HTML
pages in your browser, or run applications in executable form.
Recording in an existing script
With Functional Tester,
you can start recording at the cursor location in the current script, which
enables you to start applications, insert verification points, and add script
support functions.
Displaying test object information
You use the Test Object
Inspector to examine graphical components visible in the running application
and display information about those objects, such as parent hierarchy, inheritance
hierarchy, test object properties, non value properties, and method information.
Getting a property value You
can get a single property value for the selected object while you are recording.
It puts a getProperty into your script and returns the value during playback.
Setting a wait state for an object This
feature is used to set a wait state for an object during playback to check
for its existence. This is useful when waiting for an object right after starting
your application, or after other actions that may take a long time.
Working with verification points
Verification points
verify that a certain action has taken place, or verify the state of an object.
When you create a verification point, you are capturing information about
an object in the application to establish this as baseline information for
comparison during playback.
Using script services
The Script Support Functions dialog box contains tabs that enable
you to insert code into the current Functional Tester script to perform a
variety of tasks, such as inserting a callScript command, a log message. a
timer, a sleep command, or a comment into a Functional Tester script.
Renaming a test asset
You can rename a Functional Tester script, test object map, or
other files in a project.
Saving test scripts and files
You can save a functional test script or file in several ways:
save the current test script or file, save all test scripts and files, save
a functional test script or file with another name in a different location.
Deleting a functional test script
You can delete a Functional Tester
script from Projects view or the Solution Explorer. Use caution, however;
deleting a script that is not under ClearCase® source control or a script
in a ClearCase dynamic
view cannot be undone.
Recording a script
To start recording scripts against
your applications, you must first configure your test environments, configure
your applications, and create a project.
Changing the default script helper superclass
By default, all Functional
Tester scripts extend the RationalTestScript class, and thereby inherit a
number of methods (such as callScript). Advanced users may wish to create
their own helper superclass which extends RationalTestScript and can add additional
methods or override the methods from RationalTestScript.