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 starcon
Date Wed, 16 Apr 2008 15:09:04 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 starcon:
http://wiki.apache.org/harmony/DRLVMInternalTests

------------------------------------------------------------------------------
  
  ''Smoke'' tests are ...
  
- ''C-unit'' tests are ...
+ ''C-unit'' tests are set of binary tests which validate Thread Manager interfaces and functionality.
''C-unit'' tests call Thread Manager functions directly from VMCore or HyThread libraries.
  
  ''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.
  
@@ -46, +46 @@

  
  There are common rules of running all of the ''DRLVM'' tests.
  
- Make sure you specify the right right configuration of DRLVM binaries (`debug` or `release`)
through `hy.cfg` property while running test, for example,
+ You can set binary configuration thought a command line option or an environment variable:
  {{{
- -Dhy.cfg=release 
+ -Dhy.cfg=[release|debug]
+ export BUILD_CFG=[release|debug]
  }}}
+ By default 'debug' mode is set.
  
- You may specify the particular run mode which is helpful while working on particular issue,
for example:
+ You may specify a run mode which is helpful while working on particular issue, for example:
  {{{
  -Dtest.mode=srv
  }}}
  
- You may specify the particular test to be run, for example:
+ Also you can specify a given test to be run, for example:
  {{{
  –Dtest.case=java.lang.ThreadTest
  }}}
  
- The known point is that if you what to run the test from direct commnd without ant adaptors,
then get this command from `ant -d` output like:
+ The known point is that if you what to run the test from direct command without ant adaptors,
then get execution command from ant debug output, for example with the following command:
  {{{
  ant -d kernel.test
  }}}
@@ -74, +76 @@

  [[Anchor(run-cunit)]]
  === 2. Running C-unit tests ===
  
- There are common rules of running all of the ''C-unit'' tests. To run all ''C-unit'' tests
in default mode need to execute from working_vm directory:
+ To run all ''C-unit'' tests in default mode need to execute from working_vm directory:
  {{{
- ant kernel.test
+ ant cunit.test
  }}}
  
- You can set binary configuration thought a command line option or an environment variable:
+ You can see test execution results at directory like:
  {{{
+ working_vm/build/windows_x86_msvc_release/tests/cunit.tests/reports
- -Dhy.cfg=[release|debug]
- export BUILD_CFG=[release|debug]
- }}}
- By default 'debug' mode is set.
- 
- Also you can specify a given test to be run, for example:
- {{{
- –Dtest.case=test_native_basic
- }}}
- 
- The known point is that if you what to run the test from direct command without ant adaptors,
then get execution command from ant debug output, for example with the following command:
- {{{
- ant -d cunit.test
  }}}
  
  [#Summary Back to Summary]

Mime
View raw message