TWiki > Dev > AutomatedTests > TestMachine	TWiki webs: Dev | Doc | Main | TWiki | Sandbox
	Dev . { Changes | Index | Search | Go }

• Requirements
• Setting up the tests
  • Download
  • Configure
  • Check
  • Automatise

Requirements

To be most useful, the tests should be done very frequently. The best is thus to have use a machine that is turned on permanently, and connected to the network. That way, you can configure it to run the tests, for instance, every day at a certain time. Everyting will happen automatically. It's also possible to install the test scipts on machine that are not turned on all the times. The tests can then either be run automatically when the machine is on (using for instance anancron), or manually, at special times, like shortly before a release.

To be able to send the results to the result page, you will need to have the rights to scp a file to the Nice project on sourceforge. As far as I know, this means being a member of the project. If you wish to set up a TestMachine, but are not a member of the project, contact DanielBonniot.

Setting up the tests

Download

First, you need to download from CVS the test scripts. Choose the directory to install the scripts in, and move into it before.

cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/nice co tester

Configure

You need to configure two files:

• The setup file.

If you need to override them, you must create a file called setup in the main directory. For instance, since my user name at home is daniel, I have a setup file with one line:

user="bonniot"

• The config.name file.

For instance, I have a file config.jdk1.4 that contains the following line:

JAVA_HOME=/usr/local/opt/j2sdk1.4.1

Check

Let's check that your installation is correct. From the main directory, type:

./run

The scripts will download the latest version of Nice, and of several applications. Then it will try to bootstrap the compiler, and to use it to compile the applications.

If all goes well, you will have in the builds subdirectory the results of the testing, in the *.res files, and the logs of the build for each configuration in the *.log files. The script has also attempted to send them to sourceforge, where they will be processed to be included in the result page. That page is generated once every hour.

If there seems to be a setup problem, look at the builds/*.log files to see what happened.

Automatise

This depend on your system. On unix, you can use crontab to configure when the tests should be run. I use the following contab entry:

20 13 * * *   (cd $HOME/OSS/tester; nice ./run)

-- DanielBonniot - 26 Apr 2003