Hi hackers.

Now that we are implementing some and compression filters we need to
design a proper way to introduce data files in the unit tests, to hold
encoded and decoded data for comparison.

I am thinking in something like this:

   - Store any data file used by the the unit tests in 

         torture/unit/data/

     Since a lot of the data files will be in binary format and since
     they may use a lot of disk space (think on large jbig2 or jpeg
     chunks, for example) we can store the files in
     www.gnupdf.org/prmgt/test-files/ and provide a little script in
     torture/unit/data/get-test-files.sh that will download the files
     to the proper place.

   - Provide some functions to ease the reading and writing of files
     to the unit tests. We can store these common functions in, for
     example, torture/unit/testlib.c

What do you thinkg about that? Suggestions?
Aleksander, would do it work with the nocheck library?



Reply via email to