-
2004.10.01 13:34 "Re: [Tiff] quad-tile", by Frank Warmerdam
-
2004.10.01 13:49 "Re: [Tiff] quad-tile", by Joris Van Damme
-
2004.10.01 13:57 "Re: [Tiff] quad-tile", by Frank Warmerdam
-
2004.10.01 14:17 "Re: [Tiff] quad-tile", by Joris Van Damme
- 2004.10.01 14:24 "Re: [Tiff] quad-tile", by Frank Warmerdam
- 2004.10.01 14:56 "Re: [Tiff] quad-tile", by Bob Friesenhahn
- 2004.10.02 14:16 "Re: [Tiff] quad-tile", by Andrey Kiselev
-
2004.10.01 14:17 "Re: [Tiff] quad-tile", by Joris Van Damme
-
2004.10.01 13:57 "Re: [Tiff] quad-tile", by Frank Warmerdam
-
2004.10.01 13:49 "Re: [Tiff] quad-tile", by Joris Van Damme
- 2004.10.03 16:01 "Re: [Tiff] quad-tile", by Frank Warmerdam
2004.10.02 17:58 "Re: [Tiff] quad-tile", by Bob Friesenhahn
- We come up with a standardized way to define the thus thought up collection of test images. A plain text based format for convinience and easy manual fiddling when necessary, is best. A testimage definition should be sufficient to easilly interpret by a LibTiff based testimage-definition to testimage-tiff-file 'converter'. It should also contain 'group' information, an identifier, a plain
Defining the tests to be performed in a simple text file (one line per test) is a wise idea. A program or script can be used to generate the actual tests. For example, there can be a script to generate a test suite which works with Autoconf/Automake. There can be another program/script which generates a test suite which is not based on Unix shell scripting (maybe a compiled test). By altering the test generator, the implementation of the actual tests can easily be adjusted.
It should also be kept in mind that script-based testing can include a common bit of code (run-time include file) which define how testing is performed. This way unnecessary replication of test code fragments can be eliminated.
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen