Automated tests

[v--]

I set up a "check" hook for running tests on this package in the corresponding PKGBUILD file in the Arch user repository. I had to figure out how to generate several fixtures myself, which was straightforward, but not trivial. Unless I am missing something, this needs to be automated.

I saw issue #18 regarding test coverage and figured that you may have plans to revise the tests in the repository. I am unfamiliar with Cython so I am unable to help without digging into it myself.

Hence this discussion - is there a concrete plan for improving the tests? If not, I can begin by setting up a pipeline for GitHub actions, and we can proceed from there.

[FriedrichFroebel]

I am not sure I can completely follow you here. https://github.com/FriedrichFroebel/python-djvulibre/blob/python3/.github/workflows/ci.yml runs automated tests on every commit, with the most relevant line being LC_ALL=C python -m unittest discover tests/ -v. This should include testing the examples as well. For reference, https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/python-modules/python-djvulibre/default.nix shows how the Nix developers are doing it.

For now, I do not have any plans to revise testing. The coverage part would be nice to have, but should mostly be about finding the right build flags for enabling coverage measurement.

Could you please elaborate which actual issues you experienced? As far as I am aware, the most important step has been to delete the djvu directory from the sdist after installing the package to avoid running against missing Cython modules.

[v--]

I figured it out. I was using the PyPI package, which does not include the .txt and .png fixtures from the repository. This lead to some wrong assumptions on my end. I will make a pull request for this.