Description

This PR adds a test harness for running end-to-end tests with Cypress.

Motivation and Context

Cypress is an end-to-end testing library that is functionally similar to our current Nightwatch test harness, but comes without the warts that Selenium and WebDriver bring, which are many.

My longer-term goal is that Cypress becomes our main avenue for end-to-end testing, and Selenium/Nightwatch is used for running smoke and regression tests relevant to cross-browser coverage through CrossBrowserTesting (cc: #4090, which has been on hold all year because we haven't been able to escape Selenium flakiness).

How Has This Been Tested?

Test the test harness?! 😱

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.