Versions Compared

Key

  • 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

...

Property

Description

Default

test-run.name

The name of the test-run. The name should match one of the files located in the build/test-runs/ directory minus the '.properties' extension.

pre-commit

results.dir

The directory where Ant stores the results of the test run.

${jikesrvm.dir}/results

results.archive

The directory where Ant gzips and archives a copy of test run results and reports.

${results.dir}/archive

send.reports

Define this property to send reports via email.

(Undefined)

mail.from

The from address used when emailing report.

jikesrvm-core@lists.sourceforge.net

mail.to

The to address used when emailing report.

jikesrvm-regression@lists.sourceforge.net

mail.host

The host to connect to when sending mail.

localhost

mail.port

The port to connect to when sending mail.

25

<configuration>.built

If set to true, the test process will skip the build step for specified configurations. For the test process to work the build must already be present.

(Undefined)

skip.build

If defined the test process will skip the build step for all configurations and the javadoc generation step. For the test process to work the build must already be present.

(Undefined)

skip.javadoc

If defined the test process will skip the javadoc generation step.

(Undefined)

...

A test-run is defined by a number of properties located in a property file located in the build/test-runs/ directory.

The property test.configs is a whitespace separated list of test-configuration "tags". Every tag uniquely identifies a particular test-configuration. Every test-configuration is defined by a number of properties in the property file that are prefixed with test.config.<tag>. and the following table defines the possible properties.

Property

Description

Default

tests

The names of the test groups to execute.

None

name

The unique identifier for test-configuration.

""

configuration

The name of the RVM build configuration to test.

<tag>

target

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

"main"

mode

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

""

extra.args

Extra arguments that are passed to the RVM.

""

extra.rvm.args

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".

...