| 14 |
|
units (since PyUnit was designed to test Python units, not C). |
| 15 |
|
A C-level testing framework may be added later. |
| 16 |
|
|
| 17 |
+ |
There's no good way to automatically test GUI programs like |
| 18 |
+ |
rview. We have to rely on good human testers to check whether |
| 19 |
+ |
those work correctly or not. |
| 20 |
|
|
| 21 |
+ |
|
| 22 |
|
Requirements |
| 23 |
|
|
| 24 |
|
You need a working installation of Python 2.1 (or newer) on your |
| 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. |
| 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 |
| 62 |
|
can supply it to the python interpreter as its single argument: |
| 87 |
|
|
| 88 |
|
If any of the tests fail on your platform, please report your |
| 89 |
|
results (and as much ancilliary information about your system and |
| 90 |
< |
Radiance version) to the radiance code development mailing list: |
| 91 |
< |
http://www.radiance-online.org/ |
| 90 |
> |
Radiance version as possible) to the radiance code development |
| 91 |
> |
mailing list on http://www.radiance-online.org/ |
| 92 |
|
The developers will then either try to fix the bug, or instruct |
| 93 |
|
you on how to refine your testing to get more information about |
| 94 |
|
what went wrong. |
| 115 |
|
series of rays against a surface under varying angles, in order |
| 116 |
|
to verify material behaviour under different parameters. Tests |
| 117 |
|
of this kind may require a custom script. |
| 103 |
– |
|
| 104 |
– |
There's no good way to automatically test GUI programs like |
| 105 |
– |
rview. We have to rely on good human testers to check whether |
| 106 |
– |
those work correctly or not. |
| 118 |
|
|
| 119 |
|
Contributed tests can be of two kinds. In the simplest case, you |
| 120 |
|
can contribute a small(!) set of test data, the command line(s) |
