Declarations address problems that arise when the components in the test program's GUI change during development.
TestNameDB
.
Name Database main window during playback
Once the test fills in the Other field, it attempts to Tab to the next field. Here is where it pauses, then (according to whatever timeout value you have selected) the script ends. The Record/Playback window shows the exception thrown by the script.
Record/Playback window with exception information
The Record/Playback window provides the following information on the failure:
suntest.javastar.lib.GUINotFoundException: JS.frame("Name Database").member("namedb") - only 5 members of type java.awt.TextField
at TestNameDB.play(TestNameDB.java:50)
TestNameDB playback completed abnormally.
From here you can see that JavaStar found only five TextField components, not the six TextFields that the script expected. This tells you where the script failed, but not why it passed up the Phone field. Your next step is to find out the type of the Phone field.
Select for Inspection window with Name field selected
This code shows:
(TelephoneTF) -
JS.frame("Name Database").member("TelephoneTF");
TestNameDB
script is trying to enter the phone data into a text field, but the application has been modified to change the Phone TextField to a component of type TelephoneTF. Unable to enter a string into a TelephoneTF, the script skips to the next TextField (Email) and enters the text field there. By the time it attempts to enter data for the Other field, no more text fields remain.
Send feedback to
JavaStar-feedback@suntest.com
Copyright © 1998
Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, CA 94303.
All rights reserved.