As the number of cypress tests increase, so does the execution time. The main purpose of mocked cypress tests is to make them efficient to execute quickly in CI and local dev env. We expect the team to produce as many more cypress tests.

During initial development it was observed that the bulk of the time consumed during cypress test execution is with the initial page load. Following cypress best practices, each test should be individually runnable (even though tests are run in sequence).

Acceptance Criteria

• investigate and implement method for avoiding long load times

Details

Theorized approach:

• Add a route to the app at the top most level that will re-render the app as if it were a new page load
  • removes asset download time
  • removes cached data held in contexts including redux
  • eg. append `#reset` to any app URL will reload the page and remove `#reset` from the hash
• Custom cypress command should be used in place of `visit` that can make use of this new route. It should perform a normal `visit` if the page is not yet loaded, otherwise use this new mechanism.