Any single Java application or applet may contain a mix of standard and custom Java objects. With Java support, you can test both types of visible Java objects in applications and applets that you develop using the Java Development Kit (JDK)/Java Runtime Environment (JRE).
If you are using the Classic Agent, you can use the setName("<desiredwindow ID>") method to create a window ID that Silk Test Classic will detect. setName() is a method inherited from class java.awt.Component, so it should work for most, if not all, of the Java classes that Silk Test Classic can detect. If you are using the Open Agent, the equivalent of the setName method is the Name property of the AWTComponent class.
By contrast, custom controls often use native properties and native methods written in Java. Increasingly, custom controls also take the form of JavaBeans, which are reusable platform-independent software components written in Java. Developers frequently design custom controls to achieve functionality that is not available in standard class libraries. You can test custom Java objects, including JavaBeans, using the Silk Test Classic Java support.
The Silk Test Classic approach to testing custom Java objects is to give you direct access to their native methods and properties. A major advantage of this methodology is that it obviates the need to write your own native methods.
The procedure for testing custom Java objects is simple: Record a class for the custom control, then save the class definition in an include file. The class definition includes the native methods you can call and native properties you can verify from your 4Test script.
The predefined property sets supplied with Silk Test Classic have not been customized for Java; however, you can modify these property sets. For additional information about editing existing property sets or creating new property sets, see Creating a Property Set.