To enter Record mode:
Record Test Script window
Type the filename directly into the Create script field, or browse to locate a test you want to overwrite. JavaStar creates a .java
and .class
file for the name you provide.
For a description of non-components, locators, and to learn how and when to use them, see the chapter "Locators for Non-Components." You need to read this chapter if you are testing an application or applet that uses a toolkit that does not derive from Java AWT.
Note - JavaStar provides locators for the Bongo and IFC toolkits.
This feature is useful if you've already recorded declarations for your program under test and have edited those declaration files to use abstracted names. By specifying the declaration files you want to use, you set JavaStar to record using these files, instead of using default component names.
To specify the declarations files you want to use, click Map list... to select from a list. If you can't locate declarations you know you recorded, check to see if you have compiled the declarations into .class
files.
Note - You can learn more about declaration files in the chapter "Generating and Using Declarations."
When you record with delays, JavaStar notes the length of any delay between recorded events and includes that delay in the test. Usually recording with delays is not necessary, but if your application has a Canvas component, or if it uses a non-AWT toolkit without a Locator, you need to toggle this option on. If delays aren't important to your test, leave this option off.
The Record/Playback window opens (see Figure 4-2). The action buttons appear along the left side of the window.
Record/Playback window during record mode
JavaStar records your actions and dynamically displays the Java code it generates in the log panel.
Send feedback to
JavaStar-feedback@suntest.com
Copyright © 1998
Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, CA 94303.
All rights reserved.