Jump to: navigation, search

Common Build Infrastructure/Testing

< Common Build Infrastructure
Revision as of 16:43, 1 February 2010 by Nickboldt.gmail.com (Talk | contribs) (References)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Draft Content
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.

Running Tests As Part Of An Athena Build

Simply use these build.steps entries to build, then run, your tests. Or omit the property entirely in your build.properties file and the default steps will be run:


Note that the previous test runner task, "test" is still available but only works on Linux as it requires xvnc or xfvb.

Run Tests In Hudson

To use the new testLocal task, you will need to enable Xvnc to run around your entire build.


To use the old test task, you will need to run your tests on a Linux server with xvnc or xvfb installed.

Running Tests Separately From An Athena Build

Option 1. Run Tests Again

After a successful build, you may want to re-run the same tests.

Point your build.properties at the previous build's timestamp and it will re-run the tests in that same folder (destructively).


Yes, that's it - just point at a pre-existing timestamp, and you're good to go!

Option 2. Run Tests Separately From a Previous Build

Point your build.properties at the paths where the Tests and Update zips can be found.

If you normally build with repositoryURLs and featureIDsToInstall, add the values below to those existing properties - DO NOT replace! You will of course need to define all the runtime/compiletime dependencies as you would for a normal build or build+test run.

Local Inputs


Remote Inputs


To prevent cleanup, you can either omit the build.steps=publish,cleanup steps, or use



Controlling Test Environment

You can pass a custom library file (to replace org.eclipse.test/library.xml) or set different Java heap/permgen settings when running your tests. This is particularly important when debugging or running on 64-bit platforms, which need more memory allocation than 32-bit platforms. See Testing - VMArgs for details.