You can run the tests with IntelliJ, Maven or Eclipse.
Go to the src/test/java package, right click on it and select the “execute tests” option.
Go to the root of the project, right click on it and select: “run as” and then “junit test”.
Make sure that you have the Java Home Path exported. The JDK version should be 17 (in our case, we are using the OpenJDK one). In case you have to configure it on linux you can do:
$ export JAVA_HOME=/usr/lib/jvm/java-17-openjdk/
After that, go to the root of the project and execute:
$ mvn test
Before contributing, see the issues page for knowing which changes/improvements can be made to the project. After you’ve choosen the problem you want to fix, you have to assign yourself to the issue. After that, create a new branch with your name (for example: pablo), and commit your changes to it. When you have finished your work, you can nominate all the project members inside the issue and then, if everything goes fine, you will merge your branch with develop. If you want to see if some issue has already been talked inside the repository, you can go to the clossed issues tab.
For know, the only “issue” we have is that github actions can’t execute the PDFDocumentTest class. This is because github actions runs on a server that doesn’t have a display server like Xorg installed, which is necessary for openning a pdf file.
For fixing this, we’ve created another maven configuration file just for github actions. This file ignores the PDFDocumentTest class and tests all the other classes. This is a hack that we would like to fix, but we hadn’t have more time.