Improve Testing

[scissorsneedfoodtoo]

Currently the Cypress tests use local JSON page and post files sourced from the English Ghost instance (Content API, v3).

Going forward, we'll want to set up a Docker instance of Ghost with the following:

• Articles, tags, and at least two authors (one for regular posts, another to act as a translator for a later feature)
• A preconfigured Content API key for 11ty to use during test builds

Once the Dockerized Ghost instance has been set up, we'll need to:

• Create a SQL dump and zip it
• Create a workflow / modify the Cypress test GH Action (still in progress) to spin up the Docker container and restore the dump
• Run the Cypress tests once the dump has been restored

We should also have detailed documentation on how to start the Docker image, unzip and restore the SQL dump locally, make modifications (add more articles, authors, and so on), and create / zip a new SQL dump.

Tasks

• Use Dockerized Ghost instances for Cypress test suite. Closed via feat: Dockerized Ghost #207
• Write tests for pre-production containers, and adjust workflow to run tests before the deployment step

[raisedadead]

@scissorsneedfoodtoo and I discussed that we would start by using pre-production instances of the containers (staging platform) that we have built already. We would essentially have an interim step between the build and deployments where we can run Cypress tests on the staging before the deployments happen on production.

Kris will be working on the tests, and once it's ready, we can hash out the workflow files for the logic above.