Create test environment for new Directory

[SteelWagstaff]

We have E2E tests built with Nightwatch and our selectors. When the DOM changes, the E2E tests will need to either a) update the selectors or b) be rebuilt using a different testing framework.

Oscar proposed moving tests to Cypress for new front end.

• [x] Make a decision about what to use for E2E testing -- Cypress.io!
• [x] Create simple standard index for testing (populated with ~300 records) & delete old unused testing index
• [x] Change pipeline so that dev branch runs tests against testing index
• [x] Build initial test suites for functionality delivered by base app
• [x] Create tickets for any future E2E needed but not planned as part of this sprint

[SteelWagstaff]

We will be using the Cypress framework to write E2E tests for pressbooks directory front end. Oscar and I will work on creating a testing index in Algolia with 300-500 records (probably taken from the staging index) and will delete the old testing indices in Algolia. Goal will be to produce static rather than dynamic tests, for now. Some links:

• https://cheatography.com/aiqbal/cheat-sheets/cypress-io/
• https://www.browserstack.com/docs/automate/cypress
• Safari support in Cypress: https://github.com/cypress-io/cypress/issues/6422