|
The issue doesn't have to do with parsing content (I wish!), but I was able to write a fully encapsulated unit test for the problem - hopefully this will help track down the root issue.
I have submitted the unit test: test/core/com.lowagie.text.pdf.TestPdfCopyAndStamp
Would someone be willing to give it a run and see if they can spot the problem?
Core issue is described here: http://www.mail-archive.com/itext-questions@lists.sourceforge.net/msg40950.html
I'm not sure if this issue would be considered to be exotic or not - it seems like a pretty common use case. Again, I wish I could bring a solution to the table, and not just a problem...
Thanks,
- K
----------------------- Original Message -----------------------
From: Xavier Le Vourch <[EMAIL PROTECTED]>
To: iText Developers <[EMAIL PROTECTED]>
Cc:
Date: Thu, 13 Nov 2008 12:14:51 -0800
Subject: Re: [Itext-developers] Policy for adding unit tests?
Kevin Day wrote:
> I have a unit test that shows a problem with PdfCopy (it leaves off xobject content streams in certain situations). > > Some OS projects I work on don't want unit tests uploaded unless there is a fix available, > others prefer to have the unit test so they know they have a problem. > > Unfortunately, my digging so far has not brought me to a point where I'm able to determine > root cause or suggest a fix. > > What is the iText policy, and should I commit the test? I don't think there's a policy in place as unit testing is a pretty recent addition and it's not that easy to test the generated pdf files. Testing the parsing of pdf should be easier to automate though... FYI, in the PMD project, I've added a flag to some tests and we have two ant targets, "test" and "regress". "regress" tests should not fail and if they do, the build fails and the hudson CI serv er will notify the developers. "test" on the other hand contains all the "regress" tests plus some exotic cases that are not solved yet and do not block a new release. I believe it's better to have them there than commented out as it used to be. I could implement the same framework for iText, with maybe making "test" be the regression test and creating a new target for the extra tests that may fail but will not prevent a new release. Xavier -- Xavier Le Vourch Brittany Software, Inc. <[EMAIL PROTECTED]> PGP Key (ID 0x896C5947): http://brittanysoftware.com/gpg_key.asc Key fingerprint: 73B3 6370 B8C5 4325 F2D8 4115 0372 5805 896C 5947 ------------------------------------------------------------------------- This SF.Net email is s ponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=""> _______________________________________________ Itext-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/itext-developers |
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://www.1t3xt.com/docs/book.php
