There have been a number of occurrences[1][2][3][4][5][6][7][8] of catastrophic errors in Internet Explorer which would be immediately obvious on any attempt to load the block editor. In lieu of running the full set of end-to-end tests, we should explore a minimally viable solution to verify that the editor loads without errors and displays some expected elements on the screen.

Possible approach references:

• Travis supports a Windows build environment (reference)
• Microsoft offers a Internet Explorer WebDriver tool
• If Microsoft's tool is insufficient, we could explore using the Selenium InternetExplorerDriver
• If we cannot build our own environment for testing Internet Explorer, we could consider BrowserStack-based automation (possibly free?) or similar tooling (SauceLabs, etc)