194 #All files required for the test should be in the same directory with
 195 # this file.  If converting a standalone test to run with the harness,
 196 # as long as all files are in the same directory and it returns 0 for
 197 # pass, you should be able to cut and paste it into here and it will
 198 # run with the test harness.
 199 
 200 # This is an example of running something -- test
 201 # The stuff below catches the exit status of test then passes or fails
 202 # this shell test as appropriate ( 0 status is considered a pass here )
 203 #./test # DELETE THIS LINE AND REPLACE WITH YOUR OWN COMMAND!!!
 204 
 205 if [ -d ./test_classes ] ; then 
 206     rm -rf ./test_calsses
 207 fi
 208 
 209 mkdir ./test_classes
 210  
 211 # split application classes and test plugin classes
 212 mv ./UserPluginMetadataFormatTest*.class ./test_classes
 213 
 214 $TESTJAVA/bin/java MetadataFormatTest test_classes UserPluginMetadataFormatTest

 215 
 216 ###############  END YOUR TEST CODE !!!!! ############
 217 status=$?
 218 
 219 # pass or fail the test based on status of the command
 220 if [ $status -eq "0" ];
 221    then pass "Test passed - no stack trace printing"
 222 
 223    else fail "Test failure - stack trace was printed"
 224 fi
 225 
 226 #For additional examples of how to write platform independent KSH scripts,
 227 # see the jtreg file itself.  It is a KSH script for both Solaris and Win32
 228 

 194 #All files required for the test should be in the same directory with
 195 # this file.  If converting a standalone test to run with the harness,
 196 # as long as all files are in the same directory and it returns 0 for
 197 # pass, you should be able to cut and paste it into here and it will
 198 # run with the test harness.
 199 
 200 # This is an example of running something -- test
 201 # The stuff below catches the exit status of test then passes or fails
 202 # this shell test as appropriate ( 0 status is considered a pass here )
 203 #./test # DELETE THIS LINE AND REPLACE WITH YOUR OWN COMMAND!!!
 204 
 205 if [ -d ./test_classes ] ; then 
 206     rm -rf ./test_calsses
 207 fi
 208 
 209 mkdir ./test_classes
 210  
 211 # split application classes and test plugin classes
 212 mv ./UserPluginMetadataFormatTest*.class ./test_classes
 213 
 214 $TESTJAVA/bin/java ${TESTVMOPTS} \
 215     MetadataFormatTest test_classes UserPluginMetadataFormatTest
 216 
 217 ###############  END YOUR TEST CODE !!!!! ############
 218 status=$?
 219 
 220 # pass or fail the test based on status of the command
 221 if [ $status -eq "0" ];
 222    then pass "Test passed - no stack trace printing"
 223 
 224    else fail "Test failure - stack trace was printed"
 225 fi
 226 
 227 #For additional examples of how to write platform independent KSH scripts,
 228 # see the jtreg file itself.  It is a KSH script for both Solaris and Win32
 229