-
Notifications
You must be signed in to change notification settings - Fork 218
Test result of PDF output #5670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
We had other regressions recently for automatic PDF (#6907) and PDF templates (#6900). Tasks:
|
ebruchez
added a commit
that referenced
this issue
Apr 1, 2025
ebruchez
added a commit
that referenced
this issue
Apr 1, 2025
ebruchez
added a commit
that referenced
this issue
Apr 1, 2025
ebruchez
added a commit
that referenced
this issue
Apr 15, 2025
ebruchez
added a commit
that referenced
this issue
Apr 15, 2025
- more form controls still need to be tested
ebruchez
added a commit
that referenced
this issue
Apr 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We had recently a regression with older forms that did not use calculation dependencies. and could produce a PDF with missing fields. Enabling calculation dependencies addresses the problem.
This raises the question of automatically testing PDF output. In general, this is not easy, but we could at least extract the text of the PDF with PDFBox to check the textual content.
The text was updated successfully, but these errors were encountered: