Tests?

[Hugo-Heagren]

Things to test:

• does all the data in teaching-evals conform to the spec?
• bib data tests:
  • does cv.bib conform to the datamodel? To test this, the bcf file
    has to exist, then you run something like:

    biber --configfile ./biber-tool.conf --tool --validate-datamodel cv.bib

    (see also the option --dieondatamodel) Alternatively, I could use biber to output the datamodel and then use python to validate the source against it. This might make it easier to integrate things.
  • ensure that every article has a short title to use for download slugs, and file to download (could do this by making file and shorttitle required for files in the datamodel)
  • do all the files listed in the bib file exist at their specified locations (i.e. make sure that all the paths are explicit, with respect to the git repo root)? To test this, the bib xml file has to exist.
  • article can't be /both/ marked as 'forthcoming', 'in press' etc. and have an extract date field (this is a good test to catch when it's been published but I've forgotten to change the pubstate field).
    • things like this could/should be declared in the BibLaTeX data model.
• CSS validation: https://jigsaw.w3.org/css-validator/api.html (might be worth just running it locally if I'm going to use it a lot...)
• HTML validation: https://github.com/validator/validator (this would have to happen after building though!)
• Lighthouse/axe/etc. for accessibility testing.