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

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