Hi Maruan, In my opinion, it is a good idea.
As these files are independant of PDFBox version, we could create a hierarchy of directory in http://svn.apache.org/repos/asf/pdfbox/ (not in trunk). As for PDF/A isartor test suite set of file, we could create subdirectories to group files per types of error. When we made preflight, we created a file expected_errors.txt, containing information on expected error code returned by the API. it could be a good idea to have something similar. BR, Guillaume On Sun, Dec 8, 2013 at 3:43 PM, Maruan Sahyoun <sahy...@fileaffairs.de> wrote: > > Hi, > > as we are handling and closing issues using PDFs provided by users of the > library what do you think about adding these files to a test suite if these > can be used to check for a behavior of handling specific issues. > > The benefit would be that we can write tests around these issues to ensure > that forthcoming releases are still able to handle these files. > > An idea for a naming convention would be something like <issue number><short > description> e.g. 1769-invalid_xref.pdf > > WDYT > > Maruan Sahyoun >
