The Test Composer is a lot like a work area. Here, you define which scripts you want to use, the order in which you want them to execute, and the conditions under which you want them to run. For example, at some point in your test, you might want one script to run if the previous script ended successfully, and another script--perhaps a recovery script--to run if the previous script ends with an exception. In addition, you might want the recovery script to restart the application before it executes your steps, just to make sure you return to a clean state. You can define all of this in a matter of seconds using the Test Composer's point-and-click interface.
You are not limited to using scripts within JavaStar Tests (JSTs)--you can also reference other JST files. For example, if you wanted to define an acceptance JST for your application, you might want to include a number of already-defined JSTs (maybe one that exercises each application window) as part of the test. You just reference a JST file as you would a script, and JavaStar includes it in the test.
JSTs and their nodes (the individual scripts and JSTs that make up the composed test) also accept parameters. This means that you can create highly flexible scripts and tests that you can use for a number of purposes, just by changing the parameters.
Send feedback to
JavaStar-feedback@suntest.com
Copyright © 1998
Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, CA 94303.
All rights reserved.