Recording Scripts: General Recording Tips

Recording keystrokes and mouse events is a straightforward procedure in JavaStar; once you've defined your test script name, you interact with the program you are testing exactly the way you want to test it. However, even given this simplicity, there are some important things you should know before you begin:

Make sure your record options match your needs. The Record/Playback window uses options that you can set using the Set options button on the main menu, or by clicking the Options button that appears when you're in record mode. Record options specify which actions JavaStar records and which ones the application ignores. This can be useful if you want to reduce the size of your script and your log file. You can also set options for using regular expressions to find windows and dialogs, and to use component names internal to the program under test. For more details, see Changing Options While Recording or the chapter "Customizing Options."
Don't click Stop until you are sure you don't plan any more additions to the script. Once you've stopped recording using the Stop button, you can't restart it again for that script--you can only edit the script manually. Use Pause if you want to suspend recording temporarily while you do something else. (Though, if you are not using delays while recording, leaving a test unattended for a period of time doesn't have any effect on the script.)
Don't quit or exit your application while recording. The JavaStar record activity "lives" in the same address space as your program process. While this means JavaStar can access more information about your application or applet, it also means that quitting your application kills the recording process. Rather than shutting down the test application, use the restart nodes (in Compose Test) to end and restart a program. You can write a separate test that tests the program exit conditions.