Integrate the full PDF corpus into CI
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
Research direction
This is a design-level task with no named files or tests yet. Start by reading the existing CI pipeline and the current ad hoc comparison scripts to see what runs today. Agree on the corpus access method, the 5% pixel-diff threshold and the baseline format with the maintainer before writing code. Done means a CI job runs the corpus, reports per-page diffs, and keeps failure artifacts.
Written by the indexing model from the issue text.
Description
I currently use around 70,000 PDFs for testing JPDFium, hosted on a storage VPS. Testing against this collection still relies on ad hoc scripts and manual "does this look right?" checks.
The goal is to integrate the VPS-hosted corpus into the existing CI pipeline and make these checks automated and reproducible. This should cover document loading, rendering, and relevant editing operations, with clear reports and retained failure artifacts to make regressions easier to investigate.
Notes on visual testing:
Compare rendered output against baseline images and flag differences above a threshold. For example, flag a page when more than 5% of its pixels differ, and include the baseline, actual output, and a diff image in the report.
Comparisons should account for the expected effects of each operation. For example, a redaction test should verify that the intended area changes while the rendered content outside it remains unchanged.
Notes on structural testing:
Run qpdf --check and similar validation tools on both the input and output PDFs, capturing their exit codes, warnings, and errors. Compare the results to see pre-existing problems in the source documents from new issues introduced by JPDFium.
These checks should complement visual and operation-specific tests. Passing qpdf --check (or the equivalent of other CLI PDF binaries) does not guarantee that a PDF renders correctly or that an editing operation produced the intended result (see: qpdf read the docs) BUT may give some hints when something is going in the wrong direction.
- Dominant language
- Java
- Stars
- 16
- Forks
- 4
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 56
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Stirling-Tools/JPDFium
-
vips-drift
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Stirling-Tools/JPDFium#300 ·
Maintainers usually reply within 1 day
-
pdfium-drift
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Stirling-Tools/JPDFium#299 ·
Maintainers usually reply within 1 day
-
Split up some of the bridge files, as their sizes are getting out of handPossibly taken @balazs-szucs claimed this 2 days ago. Open
Stirling-Tools/JPDFium#279 · 1 assignee ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
Stirling-Tools/JPDFium#276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Stirling-Tools/JPDFium#192 ·
Maintainers usually reply within 1 day
All issues in Stirling-Tools/JPDFium
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/skywalking#14239 ·
Maintainers usually reply within 1 day
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Possibly taken @dbusche claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
h2database/h2database#4580 ·
Maintainers usually reply within 1 day
-
hermes-queue
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Maintainers usually reply within 1 day
-
Guidelines: document how to build a use case against a local, unpublished Flow/browserless-test changePossibly taken @totally-not-ai claimed this today. Open
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
vaadin/use-cases#452 · 1 comment ·
Maintainers usually reply within 1 day
-
area/storage area/storage/sql
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Apicurio/apicurio-registry#11159 ·
Maintainers usually reply within 1 day