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 Vladimir Beliaev
Date Wed, 16 Apr 2008 13:51:56 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 Vladimir Beliaev:
http://wiki.apache.org/harmony/DRLVMInternalTests

------------------------------------------------------------------------------
  [[Anchor(Summary)]]
  === Summary ===
  
- [#Status Status]
+ [#Status Status] [[BR]]
+ [#Build Building DRLVM tests] [[BR]]
+ [#run-smoke Running Smoke tests] [[BR]]
+ [#run-cunit Running C-Unit tests] [[BR]]
+ [#run-kernel Running Kernel tests] [[BR]]
+ [#run-unit Running Unit tests] [[BR]]
  
  [#Summary Back to Summary]
  [[Anchor(Status)]]
@@ -14, +19 @@

  
  ''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.
  
- ''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''. 
+ ''Smoke'' tests are ...
  
+ ''C-unit'' tests are ...
+ 
+ ''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.
+ 
+ ''Unit'' tests are ...
  
  ''DRLVM tests'' located in directories three started from `trunk/working_vm/tests`.
  
+ [#Summary Back to Summary]
+ [[Anchor(Build)]]
+ === Building DRLVM tests ===
+ 
+ To build ''DRLVM tests'' you need just to run them in any configuration. For example, to
be ''Kernel'' tests you may execute the following:
+ {{{
+ cd trunk/working_vm
+ ant -Dhy.cfg=release -Dtest.mode=jet kernel.test
+ }}}
+ 
+ [#Summary Back to Summary]
+ [[Anchor(run-smoke)]]
+ === Running Smoke tests ===
+ 
+ [#Summary Back to Summary]
+ [[Anchor(run-cunit)]]
+ === Running C-unit tests ===
+ 
+ [#Summary Back to Summary]
+ [[Anchor(run-kernel)]]
+ === Running Kernel tests ===
+ 
+ To run all ''Kernel'' tests in all supported modes just execute from `working_vm` directory:
+ {{{
+ ant kernel.test
+ }}}
+ 
+ Note, that you need to provide the right configuration of DRLVM binaries (`debug` or `release`)
through `hy.cfg` property.
+ 
+ The extended command looks like
+ 
+ {{{
+ ant -Dtest.mode=opt –Dtest.case=java.lang.ThreadTest kernel.test
+ }}}
+ 
+ You may see the results of run at:
+ {{{
+ x-x-x-x-xx-x
+ }}}
+ 
+ [#Summary Back to Summary]
+ [[Anchor(run-unit)]]
+ === Running Unit tests ===
+ 
+ 
+ [#Summary Back to Summary]
  
  [wiki:Self:DRLVMTestTracking Back to DRLVM Test Tracking]
  

Mime
View raw message