Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3


The tests are then run on the bootstrap VM, i.e. the JVM used to build Jikes RVM. You can also configure the build to run unit tests on the newly built Jikes RVM. Note that this may significantly increase the build times of slow configurations (e.g. prototype and protype-opt).

If you are developing new unit tests, it may be helpful to run them on an existing Jikes RVM image. This can be done by using the Ant target unit-tests-on-existing-image. The path for the image is determined by the usual properties of the Ant build.

Functional and Performance Tests






The names of the test groups to execute.



The unique identifier for test-configuration.



The name of the RVM build configuration to test.



The name of the RVM build target. This can be used to trigger compilation of a profiled image



The test mode. May modify the way test groups execute. See individual groups for details.



Extra arguments that are passed to the RVM.



Extra arguments that are passed to the RVM. These may be varied for different runs using the same image.



  1. Search for one of the the following ant properties, in order.
    1. test.config.<build-configuration>.<group>.<test>.<parameter>
    2. test.config.<build-configuration>.<group>.<parameter>
    3. test.config.<build-configuration>.<parameter>
    4. test.config.<build-configuration>.<group>.<test>.<parameter>
    5. test.config.<build-configuration>.<group>.<parameter>
  2. If none of the above properties are defined then use the parameter that was passed to the <rvm> macro in the ant build file.
  3. If no parameter was passed to the <rvm> macro then use the default value which is stored in the "Default Property" as specified in the above table. By default the value of the "Default Property" is specified as the "Default Value" in the above table, however a particular build file may specify a different "Default Value".