Processing Steps
test suite
Interactive testing
For interactive testing, each individual patch can be opened in an application, and then the document preflight should be called. The visual feedback in the top section of each patch will help you to verify the preflight result: It marks clearly whether the patch content is correct according the specifications, and should not trigger an error message, or whether the patch content is not correct according the specifications, and a problem should be reported
For automated testing, all the patches can be processed separately in an automated applications, be it a hot folder based process, or a workflow system. If you setup the system as documented, then all patches will be routed to a set of output folders, and the result can be verified quickly based on the names of the patches.
Processing Steps Test Suite 1.0
This is the first release of the test suite, containing 39 test patches, and documentation on how to use the test suite.
Questions?
Curious about the Processing Steps Test Suite or wondering how it can support your work? We’d love to hear from you – get in touch with our team.