Our current front-end testing setup is insufficient to test at the level of specificity that we want. Cypress end-to-end tests are good to test critical happy paths, and Cypress component tests are good for testing widgets, but we don't have a good way to test intermediate scopes, such as a page's UI. See #2839 for an example - in this PR we ended up creating e2e tests even though the test has nothing to do with the backend.
- Figure out what kinds of assertions we care about for page-level UI
- Figure out how to use Cypress for these integration tests - do we set them up as component tests or e2e tests?
- Move relevant existing tests to this pattern.
Our current front-end testing setup is insufficient to test at the level of specificity that we want. Cypress end-to-end tests are good to test critical happy paths, and Cypress component tests are good for testing widgets, but we don't have a good way to test intermediate scopes, such as a page's UI. See #2839 for an example - in this PR we ended up creating e2e tests even though the test has nothing to do with the backend.