|P is for Practical|
PDF content and visuals testing best practicesby andreas1234567 (Vicar)
|on Dec 20, 2013 at 11:54 UTC||Need Help??|
andreas1234567 has asked for the wisdom of the Perl Monks concerning the following question:
I find myself in charge of a large number of PDF documents produced by a document production system. There is currently no automated testing. For every new release of the (buggy) document production system itself, or its' (even more buggy) document templates, we face an time-consuming, error-prone, much hated and pretty much useless please see through this pile of documents and report errors if any nightmare of a manual testing process.
Preferably, I would like to add automated tests of both the PDFs' contents and visuals, and humbly ask for the Monks' advise.
PDF content testingThe strategy is to use Xpdf (pdftotext.exe) to convert PDF into text, and then use Test::File::Contents to check the output. This works reasonable good. But alternate solutions or suggestions are welcome.
PDF visuals testingThe strategy is ... non-existant. Any assistance or guidance is highly appreciated.
PS. OS is MSWin32 but alternatives are welcome. DS.
No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them.