LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
September 2007
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2007.09.13 19:53 "Re: bug reporting and state-of-the-project query", by Bob Friesenhahn
On Thu, 13 Sep 2007, Lee Howard wrote:
> Bob Friesenhahn wrote:
>
>> What is needed are a set of small Unix shell scripts designed to fit into
>> libtiff's existing test suite. These scripts would test libtiff using the
>> libtiff utilities. Besides validating libtiff, this would help validate
>> the utilities used.
>>
>> Care to volunteer?
>
> Attached is a start.
To make things more clear, it is best to have many small tests so that
there can be a summary of the number of tests that passed/failed at
the end of the test run and one tiny failure does not cascade and
cause all tests to fail. A test is successful if it returns 0 to the
invoking environment. It is best that each test is stand-alone so
that it does not depend on the success of other tests. If there needs
to be some common test framework code (e.g. to set environment
variables) , then that can be included by simply sourcing a shared bit
of shell script.
Here is an example of one of the test scripts I used for
GraphicsMagick:
#!/bin/sh
#
# Test for 'gm' utility.
set -e # Exit on any error
. ${srcdir}/utilities/tests/common.sh
${GM} convert ${MODEL_MIFF} -raise 10x10 -label Raise Raise_out.miff
So, an example simple test for tiffinfo (assuming that file.tiff
exists somewhere) could be
#!/bin/sh
tiffinfo file.tiff > /dev/null
and for tiff2pdf
#!/bin/sh
tiff2pdf file.tiff file.pdf
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/