diff options
author | Henning Makholm <henning@makholm.net> | 2006-01-27 18:00:00 (EST) |
---|---|---|
committer | Julien Jorge <julien.jorge@stuff-o-matic.com> | 2013-01-10 16:00:40 (EST) |
commit | 7b7cd6da61b1fcc0f2a3ecce2cb9e6c42782c717 (patch) | |
tree | 98d2772f50aaddb02ac94492d2b8b151aa3e9465 /test/README | |
download | xcftools-7b7cd6da61b1fcc0f2a3ecce2cb9e6c42782c717.zip xcftools-7b7cd6da61b1fcc0f2a3ecce2cb9e6c42782c717.tar.gz xcftools-7b7cd6da61b1fcc0f2a3ecce2cb9e6c42782c717.tar.bz2 |
Import of release 0.7
Diffstat (limited to 'test/README')
-rw-r--r-- | test/README | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/test/README b/test/README new file mode 100644 index 0000000..d7d0006 --- /dev/null +++ b/test/README @@ -0,0 +1,27 @@ +This regression test requires perl, bash, and some programs from +netpbm: pngtopnm, pnmdepth and pgmtoppm. + +The expected outputs are stored as PNG files, which compress better +than just gzipped PxM, but the output from xcf2png is not compared +byte-to-byte with the stored files, because different libpng and zlib +versions may take different, but legitimate, decisions about IDAT +chunk division and compression. Instead pixel comparisions are +done with cmp(1) on PxM representations, which have less possibility +for variations. + +The test of xcftopnm assumes that the layout of the ascii header +in the output from xcftopnm matches byte-for-byte what netpbm produces. +There is an undocumented -@ switch that does this, but if you have a +wildly different version of netpbm you may need to fiddle with the +implementation of -@ and/or insert filters in the test driver +routines. + + + +There are yet no tests for correct reporting of errors. + + + +Note: display(1) from imagemagick 6.0.6.2 apparently does not display + PNG files with grayscale+alpha correctly - the alpha channel is + ignored.
\ No newline at end of file |