| 36 |
|
support files: ../lib/* |
| 37 |
|
data files: ./test data/* |
| 38 |
|
|
| 39 |
< |
This is the location where the experimental SCons build system |
| 40 |
< |
will place everything, so it might be easiest to compile Radiance |
| 41 |
< |
using SCons for testing. |
| 39 |
> |
This is the location where the SCons build system places |
| 40 |
> |
everything, which means we're testing the software after building |
| 41 |
> |
but before installing. |
| 42 |
|
The space character in the name of the test data directory is |
| 43 |
|
deliberate, because it is a design requirement that all our |
| 44 |
|
executables can handle path names with spaces. |
| 45 |
|
|
| 46 |
|
|
| 47 |
|
How to run tests |
| 48 |
+ |
|
| 49 |
+ |
The simplest way to run tests is to use the SCons build system. |
| 50 |
+ |
The file ray/INSTALL.scons explains the requirements and details. |
| 51 |
+ |
Once you have SCons working, go to the ray directory and type |
| 52 |
+ |
|
| 53 |
+ |
$> scons test |
| 54 |
+ |
|
| 55 |
+ |
which will automatically execute all available tests in the |
| 56 |
+ |
correct environment. |
| 57 |
+ |
|
| 58 |
+ |
You can also run the tests manually: |
| 59 |
|
|
| 60 |
|
On unix systems, just type "run_all.py" in this directory to |
| 61 |
|
test everything. If that file doesn't have execute rights, you |
