Differences between revisions 5 and 6
Revision 5 as of 2008-04-21 10:19:32
Size: 3535
Comment:
Revision 6 as of 2009-09-20 21:55:32
Size: 3545
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Anchor(Contents)]] <<Anchor(Contents)>>
Line 3: Line 3:
 * [#Summary Summary]
 * [#Status Status]
 * [#How_To_Run How To Run]
 * [[#Summary|Summary]]
 * [[#Status|Status]]
 * [[#How_To_Run|How To Run]]
Line 7: Line 7:
[[Anchor(Summary)]] <<Anchor(Summary)>>
Line 16: Line 16:
[[Anchor(Status)]] <<Anchor(Status)>>
Line 22: Line 22:
[[Anchor(How_To_Run)]] <<Anchor(How_To_Run)>>
Line 27: Line 27:
See [http://harmony.apache.org/subcomponents/buildtest/index.html Build-test Framework] See [[http://harmony.apache.org/subcomponents/buildtest/index.html|Build-test Framework]]
Line 55: Line 55:
Follow [http://dev.eclipse.org/viewcvs/index.cgi/test-results/platform/org.eclipse.tptp.ac.testautomation/automation-files/notes/building_tptp_jvmti_tests.txt?root=TPTP_Project&view=co&pathrev=HEAD this instructions] to get AC, checkout and build tests. Follow [[http://dev.eclipse.org/viewcvs/index.cgi/test-results/platform/org.eclipse.tptp.ac.testautomation/automation-files/notes/building_tptp_jvmti_tests.txt?root=TPTP_Project&view=co&pathrev=HEAD|this instructions]] to get AC, checkout and build tests.

Contents

Summary

TPTP test suite is used to test DRLVM JVMTI profiling support

Each test execution consists of 2 phases:

  1. Test scenario runs on tested vm with TPTP profiling agent. Profiling data is saved to xml file.
  2. Xml file generated on phase 1 is verified.

Test is considered passed if (1) test scenario was run without errors and (2) verification succeeded.

Status

The suite regulary runs with Cruise Control for 3 platforms (Windows, Linux) x86 & Linux x86_64

Current pass rate is 100%.

How To Run

1. Run with Build & Test Infrastructure

Just run tptp suite within BTI

See Build-test Framework

Note:

Exclude list is in infra/build/checkouts/tptp/exclude.list

2. Standalone run

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

3. Manual build & run

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"

4. Run single test

a. Using exclude list

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.

b. Manual run of single test scenario

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.

TPTP_Tests (last edited 2009-09-20 21:55:32 by localhost)