Package com.rational.test.ft.domain.java

Provides the proxy classes that directly access Java objects in the Software Under Test.

See:
Description

Interface Summary

IAppletViewer	An applet viewer wants to have the child applet show up in the map just like a browser does with the applet as a top level object.
IComboBox	The ComboListBoxProxy uses this interface to access the text of the items from the proxy rather than dealing with formatting issues on the specific host.
IMenuBarHost	Frames and other windows that host a heavyweight menu bar need to implement this interface so that the menu bar correlation can be performed.
IMenuManager
IPropertyFilter	Method implemented by all proxies.
ISetParent

Class Summary

ComboListBoxProxy	Proxy for the native ComboListBox windows.
DatapoolUtilities
Java2TestDomainImplementation	The "assistive_technology" class that gets loaded as an accessibility interface.
JavaBeanProperties	A helper class that provides access to java properties as defined by the java bean pattern.
JavaDomainProxy	The class for the Java Domain Proxy.
JavaGuiProxy	This is the Java GUI object proxies base class.
JavaProxy	The Java object proxy's base class, which all Java proxies must extend.
PopupMenuProxy	The implicit proxy for a heavyweight popup menu.
ProxyClassMap	This internal class loads Java domain proxies that have been registered in an RFTCUST file.
PseudoTopLevelProxy	This class does not represent a true top level proxy, it exists solely to block recording against children that can not properly respond when a popup window is displaying.
SelfRegisteredTestDomainImplementation	This class is available for Java applications that need to manually enable themselves for testing.
TestDomainImplementationJava
TestDomainJava	The Java Domain

Package com.rational.test.ft.domain.java Description

Provides the proxy classes that directly access Java objects in the Software Under Test. The base class for all AWT proxies is ComponentProxy.

Introduction

This package provides the root classes that represent object in various Java domains. The primary base implementations are the domain implementation and the proxy implementations. The domain implementations are the anchoring object for any domain and allow access to the top level proxies for each domain. The core proxy support defines default implementations for both non-GUI and GUI proxy test objects.

As a side effect of the core Java proxy implementations is a Java Beans based property definition layer. Because of the Java Beans specification we can determine which methods should be treated as properties and which should not. By definition all properties are implemented by a method that begins with get, is or has followed by a capital letter. If a property does not return a "value" type, the getProperties method will not include the property in the returned Hashtable. See TestObject.getNonValueProperties().

The values we can manage are the primitive data types and those objects defined as classes that have been registered as a value class or may be converted to a value class. Interesting properties that do not match this definition will need to be added explicitly by the proxies layered on top of this base level implementation.

Also available with the default GUI implementation are a set of standard mouse actions. For instance a default click(Point) action is provided that should be used when performing actions from proxies that extend the base implementation. These default actions will automatically ensure that the parent window has been properly activated and that the supplied Point is not obscured in any way before performing the action. Failure to use the default actions implies that the proxy takes direct responsibility for ensuring the action may be completed unhindered.

Audience

This package is for proxy writers - those who wish to customize and extend the product testing system.

@since RFT1.0