Provides input files and scripts for testing

[tarleb]

Testing the docker containers is difficult. As proposed by @svenevs, we should have at least some smoke-tests to check correctness of our builds.

Tasks that seem important enough to test:

• [ ] docx

  • [x] conversion to docx (#21)
  • [ ] conversion from docx

• [x] pdf creation via LaTeX

  • [x] simple doc
  • [x] doc's with tables, images, footnotes, custom margins, equations
  • [x] non-english language docs
  • [ ] CJK?
  • [x] Different reference backends

• [x] Lua filters which contain calls to a system-provided library

[svenevs]

Lua filters which contain calls to a system-provided library

Maybe a good excuse to actually add one of these to pandoc/lua-filters? Then we can just clone that and run that specific make test, but now also have an official example of the more hardcore things lua filters can do (provided installation supports it, re: why we are making these containers!).

[svenevs]

Testing Latex specifically, in current image for #14 I was doing some quick tests.

1. Would it be a good idea to re-use tests for the demo examples specifically:

   • Example 8: pandoc -t beamer SLIDES -o example8.pdf (worked)
   • Example 13 modified: for engine in pdflatex lualatex xelatex; do pandoc MANUAL.txt --pdf-engine=$engine -o example13_$engine.pdf; done (helped find missing lualatex-math dependency)

   These aren't exactly "simple doc" tests, but it covers the same thing -- something will compile.

2. Fancier latex tests, I wonder if we can recycle the official pandoc tests. E.g., there's quite a few table tests in there.