source: anuga_validation/automated_validation_tests/README.txt @ 7661

This directory, automated_validation_tests, contains a collection of 
projects that validate ANUGA against known scenarios either from physical 
observations or analytical solutions.

The validation tests take the form of automated unit tests except that they 
all test the whole system rather than individual components and that they
generally take considerably longer time to execute than normal unittests.

The master script, validate_all.py, will run through all tests.  

NOTE: In some circumstances there may be problems running validate_all.py
IF MORE THAN ONE PYTHON IS INSTALLED.  The workaround is to:
1. Decide which python you want to use, and get the absolute path to that
   executable ('which python2.5', for example)
2. Create a local 'bin' directory:
       mkdir ~/bin
3. Create a 'python' link in that directory to the python executable:
       ln -s <path_from_step_1> ~/bin/python
4. Create or modify your PATH variable in ~/.bashrc to include:
       export PATH=$HOME/bin:$PATH
   That is, ensure your 'local' bin is searched first
5. Remove any 'python' alias you may have defined in ~/.bashrc (or elsewhere)
6. Ensure all the above changes are in effect by opening a new terminal

The above workaround was tested under Linux.  Not sure about Windows.