harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Harmony Wiki] Trivial Update of "DRLVMInternalTests" by EugeneOstrovsky
Date Mon, 21 Apr 2008 11:46:23 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Harmony Wiki" for change notification.

The following page has been changed by EugeneOstrovsky:
http://wiki.apache.org/harmony/DRLVMInternalTests

------------------------------------------------------------------------------
- = DRLVM Internal Tests =
  [wiki:Self:DRLVMTestTracking Back to DRLVM Test Tracking]
  
  [[Anchor(Summary)]]
@@ -12, +11 @@

   1. [#run-smoke Running Smoke tests]
   2. [#run-cunit Running C-Unit tests]
   3. [#run-kernel Running Kernel tests]
-  4. [#run-unit Running Unit tests]
+  4. [#run-jvmti Running JVMTI tests]
  
  [#Summary Back to Summary]
  [[Anchor(Status)]]
  === Status ===
  
- ''DRLVM tests'' consist in ''Smoke'', ''C-unit'', ''Kernel'' and ''Unit'' tests. All ''DRLVM
tests'' are DRLVM acceptance tests so they must be run each time the contributor posts his/her
patch for DRLVM. '''It is strictly recommended''' to test your patch with ''DRLVM tests''
in both ''debug'' and ''release'' build of DRLVM on Windows/Linux/x86/x86_64 platforms.
+ ''DRLVM tests'' consist in ''Smoke'', ''C-unit'', ''Kernel'' and ''JVMTI'' tests. All ''DRLVM
tests'' are DRLVM acceptance tests so they must be run each time the contributor posts his/her
patch for DRLVM. '''It is strictly recommended''' to test your patch with ''DRLVM tests''
in both ''debug'' and ''release'' build of DRLVM on Windows/Linux/x86/x86_64 platforms.
  
  ''Smoke'' tests are set of java-language programs with standard 'main' entrance which test
different DRL VM subsystems like exceptions, GC, Threading and etc.. There are about 80 separate
tests. The source of smoke tests are in …/working_vm/vm/tests/smoke directory.
  
  ''C-unit'' tests are set of C-language tests which validate Thread Manager component. ''C-unit''
tests are dynamically linked with `hythr` to test its functionality directly without creating
full Java context. To test Java functionality of Thread Manager ''C-unit'' tests can be also
linked with `harmonyvm` library and create Java environment through invocation API. There
are 80+ tests in this suite.
  
- ''Kernel'' tests are set of java-language programs with standard 'main' entance which test
DRLVM ''Kernel Classes'' such as `java.lang.Class`, `java.lang.Thread` or features such as
Java5.0 ''Generics''. There are 660+ tests in this suite.
+ ''Kernel'' tests are set of java-language programs with standard 'main' entrance which test
DRLVM ''Kernel Classes'' such as `java.lang.Class`, `java.lang.Thread` or features such as
Java5.0 ''Generics''. There are 660+ tests in this suite.
  
- ''Unit'' tests are ...
+ ''JVMTI'' tests are intended to test DRLVM JVMTI support. Each of these tests consists of
java test class and JVMTI agent written on C++. Execution of each test class is performed
by DRLVM started with test agent.
  
  ''DRLVM tests'' located in directories three started from `trunk/working_vm/tests`.
  
@@ -110, +109 @@

  }}}
  
  [#Summary Back to Summary]
- [[Anchor(run-unit)]]
+ [[Anchor(run-jvmti)]]
- === 4. Running Unit tests ===
+ === 4. Running JVMTI tests ===
+ To run all ''JVMTI'' tests in all supported modes just execute from `working_vm` directory:
+ {{{
+ ant jvmti.test
+ }}}
+ 
+ You may see the results of run at directory like:
+ {{{
+ build/windows_x86_msvc_release/tests/jvmti.tests/reports
+ }}}
  
  [#Summary Back to Summary]
  

Mime
View raw message