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.
Before you begin
To map proxies to controls, you must explicitly map newly developed
ProxyObjects to a control or group of controls through an external map file
called customization files with the .rftcust extension. Functional Tester refers
these customization files and creates ProxyObject instances for a control
as specified in the mapping. You must create your own customization file to
specify the mapping information between the ProxyObject and the control. You
can deploy the newly created customization file by saving it in the Functional Tester customization
directory.
About this task
To map a proxy class to an AUT control class, add the
ClassName and
UsedBy tags
within the
DomainImplementation start and end tags.
Note: You
must add your proxy class name within the ClassName tag and
the name of the AUT class that the proxy represents within the UsedBy tag.
Example
The following is an example of a mapping entry in the customization
file:
<DomainImplementation L=".DomainImplementation">
<Name>Java</Name>
<ClassName>com.rational.test.ft.domain.java.awt.JSpinnerProxy</ClassName>
<Replaces/>
<UsedBy>java.awt.JSpinner</UsedBy>
</DomainImplementation>
What to do next
While updating the customization file, make sure that the file meets
the following conditions:
- Make no typing mistakes while specifying the class. The strings are case
sensitive.
- Use fully qualified class names. Use the complete class name including
the package separated with a period (.).
- Match the domain type of the proxy to the section in the customization
file by name.
- Use an appropriate XML format:
- Nest start and end tags properly.
- Specify names for tags (case is significant).