Rational Functional Tester proxy SDK
Extend automated functional testing support for your application's
user interface controls.
- Introduction to proxy SDK
With Rational® Functional
Tester proxy software development kit (SDK) you can extend automated functional
testing support for your application's user interface controls (GUI test objects),
beyond what is provided by Functional Tester by
default. The proxy SDK provides detailed documentation, API references and
ready-to-use samples and tutorials on how to extend Functional Tester to
add support for testing new controls. It also helps you to extend already
supported controls from the existing domains.
- Functional Tester architecture
Rational Functional Tester can be extended
to perform additional functions for which it needs to communicate with the
application under test (AUT). To do that Functional Tester first
establishes a communication channel to the AUT which is called enablement.
- Proxy development
A challenge in functional testing is the variety of user interface
(UI) frameworks that are available (for example, Java™ and HTML) and controls (for example,
button and table) that testing must support. UI frameworks differ in architecture
and programming models and the controls differ in their inheritance hierarchy,
methods, properties data, and user actions.
- Mapping proxies to controls
Functional Tester identifies each
application under test (AUT) control by its class name. Running the testObject.getProperty(".class") method
in the test script gives you the class name. The mapping is established through
the class names of the respective control and ProxyObject.
- TestObjects
TestObjects are the script-side interfaces for proxies and application
under test (AUT) controls. A TestObject is a connection point between the
test script and a ProxyObject that connects to the real object in the AUT.
During recording, statements are recorded and objects are added to the Object
Map. The script uses the information from the Object Map to construct and
find TestObjects.
- Deploying a proxy
After you have developed the proxy binary and customization files,
you must deploy them for the changes to take effect.
- Debugging the proxy code
Debugging the proxy code is an essential part of the proxy development
process for problem determination. The proxy code containing the JAR file
or .Net assembly file with the .dll extension is loaded into the application
under test (AUT) process. To debug the proxy code, attach the respective debugger
to the AUT process after the proxy binary files are loaded into the AUT.