Lucas-C
commented
1 week ago Thank you for starting working on this subject, an welcome on board @cyy-2024! 🙂
First, I would warmly recommend to start initiating some unit tests quite early, in the spirit of test-driven_development. This is a good habit to have when writing software, especially when unit tests are expected in the end for the piece of code you are writing.
You can start with 2 base unit tests:
- one simple unit test where every thing goes well, and you have a final assertion that checks that the signature of the forged PDF can be validated with
endesive - one failing test case, for example for the case where the
.p12cannot be open due to a wrong password being provided
cyy-2024
Hello, I added a new sign file and modified the cil file. I also provided a p12 file of the test. You can run the following commands on the CMD：pdfly sign input.pdf --output signed_output.pdf --p12 certs.p12 --password "123456"。
This results in a PDF that retains the original PDF and adds the signature text and signature information.
If you have any questions, please ask, thanks for giving me the opportunity!