Spike: Frontend unit and end-2-end testing #269
Description
User Stories:
As a developer, I would like to have confidence that the frontend React components are working as expected.
As a developer, I would like a way to test the application as a functional product.
Overview:
The goal of this story is to get more enjoyable testing for our application. We need to add the ability to write tests that verifies that our frontend is working as expected. Having tests will give us confidence that we are writing new features that does not break existing workflows.
Talking with Alex, there has been a goal to get testing enabled using Cypress. Cypress touts itself as an all-in-one solution for testing, but in my expertise I would state that Cypress more closely aligns with end-2-end testing frameworks. Being able to test the application as a whole product will allow developers unfamiliar with testing to better understand how their automated tests align with the application.
There is a second component to adding Cypress, which revolves around making sure that all of our baseline testing is working. In an effort to make sure that we are not stepping on our own toes for later down the line, I would like to see that our unit tests in the frontend are minimally functional.
Lastly, we need to make sure that the entry points to testing in the various areas of the application is functional.
Acceptance Criteria:
[ ] We have working Jest tests in the frontend
[ ] We have working Jest tests in the backend
[ ] We have a working end-2-end test suite (likely Cypress)
[ ] Make sure that all test runners are working as expected.
[ ] Update the README and relevant end documentation.