TPTP test suite is used to test DRLVM JVMTI profiling support
Each test execution consists of 2 phases:
Test is considered passed if (1) test scenario was run without errors and (2) verification succeeded.
The suite regulary runs with Cruise Control for 3 platforms (Windows, Linux) x86 & Linux x86_64
Current pass rate is 100%.
Just run tptp suite within BTI
Note:
Exclude list is in infra/build/checkouts/tptp/exclude.list
Checkout tptp runner scripts:
svn co http://svn.apache.org/repos/asf/harmony/enhanced/buildtest/trunk/tests/tptp |
in tptp directory run:
ant -Dtested.jre=$TESTED_JAVA_HOME |
or in 2 steps:
ant setup // obtain prerequisites and build ant -Dtested.jre=$TESTED_JAVA_HOME run // run tests |
See the report in tptp/results directory.
Note:
Exclude list is in tptp/exclude.list
Follow this instructions to get AC, checkout and build tests.
To run the tests use the following command:
${JAVA_HOME}/bin/java \ -Dtest.param="${EM_OPT}" \ -Dtest.timeout=${test.timeout} \ -Dconfigfile="$CFGFILE" \ -Dtest.output=${OUTPUT} \ -Dtest.java=${UT_RUNTIME} \ -Dtest.home=${TEST_HOME} \ -Dac.home=${AC_HOME} \ -Dtest.verbose=false \ -Xbootclasspath/p:${BOOTCLASSPATH} \ -classpath ${CLASSPATH} \ org.eclipse.tptp.ac.testautomation.AllStandaloneProfiling > ${OUTPUT}/log.txt 2>&1 |
where:
JAVA_HOME - reference runtime location EM_OPT - running mode for DRLVM -Xint/-Xem:opt/-Xem:jet or default + -XX:vm.assert_dialog=false for RI it is empty TIME_OUT - time in milliseconds for 1 test CFGFILE - configure file location. E.g. org.eclipse.tptp.ac.testautomation/automation-files/config/local_config_file.xml OUTPUT - output directory location UT_RUNTIME - tested JRE location TEST_HOME - tests directory location AC_HOME - agent directory location BOOTCLASSPATH - used bootclasspath CLASSPATH - used jar files |
Note:
To exclude tests modify configuration xml file: $CFGFILE
For specific "<test_case>" node change "execute" attribute from "yes" to "no"
To run single test you should add all the tests except the one you need to the exclude list.
Then run suite with one of the preceding methods.
You may also run the test scenario with tested jre using the command line and environment provided in any test report file.
This is not a complete test run because profiling data verification will not be performed. However this method is good for debugging VM crashes during scenario execution.