... | ... | @@ -7,21 +7,21 @@ Reliability in the face of complexity is the real challenge of software developm |
|
|
|
|
|
## Download and explode the test cases
|
|
|
|
|
|
The input files are in the directories below tsuite in the distribution.
|
|
|
The output is in [this]( ftp)http://data.nublado.org/cloudy_releases/) directory.
|
|
|
The input files are in the directories below tsuite in the distribution.
|
|
|
The output is below [this](http://data.nublado.org/cloudy_releases/) directory.
|
|
|
|
|
|
There are four directories below tsuite in the distribution.
|
|
|
These contain different types of tests.
|
|
|
These contain different types of tests.
|
|
|
Those in the *auto* directory are run every night in Lexington.
|
|
|
These are a large number of simulations that test some aspect of the physics.
|
|
|
These are a large number of simulations that test some aspect of the physics.
|
|
|
The tests in the *slow* directory take about three days and are continuously running on machines here.
|
|
|
The directories under *programs* contain programs that call Cloudy as a subroutine.
|
|
|
The directories under *programs* contain programs that call Cloudy as a subroutine.
|
|
|
Finally, the *crash* directory contains a series of tests that should cause the code to
|
|
|
crash if it has been compiled correctly.
|
|
|
|
|
|
Each directory contains several Perl scripts and html files.
|
|
|
The *readme_*.htm* files describe the contents of each directory.
|
|
|
The file *doc_tsuite.htm* documents the purpose of each of the tests.
|
|
|
Each directory contains several Perl scripts and html files.
|
|
|
The *readme_*.htm* files describe the contents of each directory.
|
|
|
The file *doc_tsuite.htm* documents the purpose of each of the tests.
|
|
|
It could be studied to see how to set up the code.
|
|
|
|
|
|
The tests should not be placed in a directory that contained an older version until the old version is first deleted. The names of the test cases change from time to time and placing the current version of the suite on top of an old one will not overwrite all the old ones. This will cause problems when the test suite is run. Either start with a new directory or first delete the contents of the directory.
|
... | ... | |