Differences between revisions 35 and 36
Revision 35 as of 2008-05-20 12:16:54
Size: 1887
Revision 36 as of 2009-09-20 21:55:24
Size: 1751
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
  * [wiki:Self:HUT Classlib tests]
  * [wiki:Self:DRLVMInternalTests DRLVM tests (Smoke, C-Unit, Kernel, JVMTI)]
  * [[HUT|Classlib tests]]
  * [[DRLVMInternalTests|DRLVM tests (Smoke, C-Unit, Kernel, JVMTI)]]
Line 17: Line 17:
  * [wiki:Self:TPTP_Tests Eclipse TPTP Tests]
  * [wiki:Self:JDKTools_Tests JDKTools Tests]
  * [wiki:Self:VTSVM_Tests VTSVM Tests]
  * [wiki:Self:Functional_Tests Functional Tests]
  * [wiki:Self:DRLVMRegressionTests Regression tests]
  * [[TPTP_Tests|Eclipse TPTP Tests]]
  * [[JDKTools_Tests|JDKTools Tests]]
  * [[VTSVM_Tests|VTSVM Tests]]
  * [[Functional_Tests|Functional Tests]]
  * [[DRLVMRegressionTests|Regression tests]]
Line 27: Line 27:
  * [wiki:Self:Reliability_Tests_on_DRLVM Reliability Tests on DRLVM]
  * [wiki:Self:Stress_Tests Stress Tests]
  * [[Reliability_Tests_on_DRLVM|Reliability Tests on DRLVM]]
  * [[Stress_Tests|Stress Tests]]
Line 34: Line 34:
  * [wiki:Self:Apache_Axis Axis scenario on DRLVM]
  * [wiki:Self:
Eclipse_Unit_Tests Eclipse Unit Tests on DRLVM]
  * [wiki:Self:
Eclipse_Scenarios Eclipse Geronimo Application on DRLVM]
  * [wiki:Self:
GUT_Tests Geronimo Unit Tests on DRLVM]
  * [wiki:Self:
struts_test Struts scenario]
  * [wiki:Self:Tomcat_scenario Tomcat scenario]
  * [wiki:Self:
JettyScenario Jetty scenario]
  * [wiki:Self:
SciMarkBenchmark SciMark2.0]
  * [[Apache_Axis|Axis scenario on DRLVM]]
  * [[
Eclipse_Unit_Tests|Eclipse Unit Tests on DRLVM]]
  * [[
Eclipse_Scenarios|Eclipse Geronimo Application on DRLVM]]
  * [[
GUT_Tests|Geronimo Unit Tests on DRLVM]]
  * [[
struts_test|Struts scenario]]
  * [[Tomcat_scenario|Tomcat scenario]]
  * [[
JettyScenario|Jetty scenario]]
  * [[
Line 43: Line 43:
Thanks [[BR]] Thanks <<BR>>

The Harmony team processes the regular Automated Testing of snapshots using the workloads groups below.

The groups are:

Acceptance Tests

These tests must be run by contributor before submitting the patch to JIRA. Basically "Classlib tests" are run against ther patches for working_classlib code and "DRLVM tests" are run against code located at working_vm.

Features / Specification tests

Harmony project uses set of test suites to check Virtual Machine and Java Class libraries functionality. the following suites are used for this:

Stability / Reliability tests

There are test suites to check DRLVM stability / reliability which are:

Application oriented scenarious

Harmony was turned to run different applications. We are checking that these application are kept supported with the help of following workloads / scenarious:

Apache Harmony Team

DRLVMTestTracking (last edited 2009-09-20 21:55:24 by localhost)