Integration Test in preflight to make easy validation
-----------------------------------------------------

                 Key: PDFBOX-1105
                 URL: https://issues.apache.org/jira/browse/PDFBOX-1105
             Project: PDFBox
          Issue Type: Improvement
          Components: Preflight
            Reporter: Guillaume Bailleul
            Assignee: Guillaume Bailleul
             Fix For: 1.7.0
         Attachments: padaf-integ.patch

I join a patch that add 3 Test to :
- check isartor files and check if expected error occurs
- check invalid files and check (if defined) if expected error occurs
- check valid files 
pom.xml is modified to set these test as integration test.

If nothing is configured, integration phase does not fail.
If parameters are configured, directories with pdf files are pointed and test 
should fail is configuration is invalid

Parameters are :
* isartor.files = path of isartor files
* expected.errors = the file that contains expected error codes (see 
preflight/src/test/resources/expected_errors.txt)
* invalid.files = path of directory containing file known as invalid
* invalid.errors = a file that can contain expected error code for invalid 
file, this is not mandatory
* valid.files = path of directory containing file known as valid
Use -D... to set parameters.

I will not commit that patch quickly because I am not sure it is the best way 
to do. With this method, there is no PDF/A file in generated artefacts so no 
licence problem. Anyone can have his set of file to validate preflight even if 
I could be a good idea to share when possible ... But I don't known where.

So if anyone has suggestion to help ...

sha1sum : d1694158976f7f6e69f893be149b7a1bb9a6a714  padaf-integ.patch





--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to