< prev index next >

test/hotspot/jtreg/vmTestbase/vm/runtime/defmeth/README

Print this page




 114         - ConflictingDefaultsTest
 115         - DefaultVsAbstractTest
 116         - MethodResolutionTest
 117         - ObjectMethodOverridesTest
 118         - PrivateMethodsTest
 119         - RedefineTest
 120         - StaticMethodsTest
 121         - StressTest
 122         - SuperCallTest
 123 
 124     Each test group can be executed in different modes. For each mode there's a
 125     corresponding scenario in src/vm/runtime/defmeth/scenarios.
 126 
 127     Scenarios are organized in the following manner:
 128 
 129         .../scenarios/[test_group]_[majorVer]_[methodFlags]_[invocationType]_[shouldRedefine]
 130 
 131     where
 132 
 133         majorVer - major version of class files for generated concrete classes
 134             values: ver49, ver50, ver51, ver52
 135 
 136         methodFlags - additional access flags for methods in generated classes
 137             values:
 138                 none == no additional flags
 139                 sync == ACC_SYNCHRONIZED
 140                 strict == ACC_STRICT
 141                 syncstrict == ACC_SYNCHRONIZED | ACC_STRICT
 142 
 143         invocationType - how methods in test hiearchies are invoked during testing
 144             values:
 145                 direct - using invoke* bytecodes
 146                 reflect - using Reflection API
 147                 invoke - using invokedynamic & java.lang.invoke API (MethodHandles/JSR292)
 148 
 149         redefine - whether to preload and redefine classes before running individual tests
 150             values: redefine, noredefine
 151 
 152         testGroup - name of test group being used
 153             values: BasicTests/BridgeMethod/etc
 154 




 114         - ConflictingDefaultsTest
 115         - DefaultVsAbstractTest
 116         - MethodResolutionTest
 117         - ObjectMethodOverridesTest
 118         - PrivateMethodsTest
 119         - RedefineTest
 120         - StaticMethodsTest
 121         - StressTest
 122         - SuperCallTest
 123 
 124     Each test group can be executed in different modes. For each mode there's a
 125     corresponding scenario in src/vm/runtime/defmeth/scenarios.
 126 
 127     Scenarios are organized in the following manner:
 128 
 129         .../scenarios/[test_group]_[majorVer]_[methodFlags]_[invocationType]_[shouldRedefine]
 130 
 131     where
 132 
 133         majorVer - major version of class files for generated concrete classes
 134             values: ver49, ver52
 135 
 136         methodFlags - additional access flags for methods in generated classes
 137             values:
 138                 none == no additional flags
 139                 sync == ACC_SYNCHRONIZED
 140                 strict == ACC_STRICT
 141                 syncstrict == ACC_SYNCHRONIZED | ACC_STRICT
 142 
 143         invocationType - how methods in test hiearchies are invoked during testing
 144             values:
 145                 direct - using invoke* bytecodes
 146                 reflect - using Reflection API
 147                 invoke - using invokedynamic & java.lang.invoke API (MethodHandles/JSR292)
 148 
 149         redefine - whether to preload and redefine classes before running individual tests
 150             values: redefine, noredefine
 151 
 152         testGroup - name of test group being used
 153             values: BasicTests/BridgeMethod/etc
 154 


< prev index next >