The last thing to do is to examine the results of the test run. This section shows you how to view and filter the results of a single script.
TestNameDB
script, the Results Viewer should have this script already loaded.
Results Viewer
The Summary for TestNameDB
should show 1 normal condition and 7 verifications that passed. The normal condition tells you that the script itself ended normally--the synchronized comparison did not throw an exception. If this was a test composed of multiple scripts, you might see several normal conditions and some exception conditions in the summary, because JavaStar tracks the end state of each script.
A verification error can occur in a number of circumstances--such as when JavaStar can't find an auxilary file it needs for the test--and you should check the log file for a specific message. JS.check pass/fail conditions reflect the results of custom code that you can insert (using the JavaStar API check method of the JS class) to track your own conditions. You did not add any custom code to the test you just ran, so all the values are 0.
Note - The chapter "Using the JavaStar API" discusses the JavaStar API and shows how you can incorporate API methods into your scripts.
Here you can see the comparisons this test executed. The Results Viewer displays these in brief form, because the Shortened lines option is selected, by default. The + sign next to each event means that you can see more information by clicking on the line to expand it. Experiment with expanding and contracting this information, or turning off Shortened lines and reloading the file to see complete information for each event.
You can find the Process Information checkbox at the bottom of the Details panel.
By default, the Results Viewer filters out:
This example of the Results Viewer doesn't show the full value of the tool, mainly because it does not demonstrate results for nested JST (JavaStar Test, or composed test) files, and there were no failures in this test.
In later chapters, you'll see how JavaStar shows results for JSTs within an expandable/collapsible tree, and the summary information will be more helpful. Comparison failures are harder to demonstrate, because you'd have to edit the script to force it to fail in order to move through failures using the Next Failure button. Refer to the chapter "Viewing and Analyzing Results"in the JavaStar User's Guide for details on viewing failures and updating comparisons.
Send feedback to
JavaStar-feedback@suntest.com
Copyright © 1998
Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, CA 94303.
All rights reserved.