Add E2E tests (to the CI)

They're definitely working locally using Selenium & things, but getting it to run on the CI will be a bit of a pain since I'm halfway across the world from the network/machines. Steps:

• Clone beat.tutorial.prefix and use the prefix folder for the tests
• Figure out how to run the beat.editor REST server in the testing environment
• Figure out how to expose the geckodriver executable (different for Mac & Linux!) and add it to the $PATH

changed milestone to %JS & Python Testing

added in-progress label

Looks like this might work! I got selenium running with firefox headless, so I think it might work on the CI. The only issue might be the CI not liking the python server running.

To run the e2e tests you'll need the geckodriver executable available in your path: https://github.com/mozilla/geckodriver/releases/

mentioned in commit d11f2d3d

changed title from Add E2E tests to Add E2E tests (to CI too)

changed title from Add E2E tests (to CI too) to Add E2E tests (to the CI)

changed the description

This is pretty iffy because selenium is pretty flaky when being ran in a headless browser. Unfortunately I think I'd have to recommend not enabling the E2E on the CI because there's too many false negatives - sometimes selenium will just fail with a random but valid-looking error. It'll also randomly start hanging and never finish.

Running the testing non-headlessly seem to have no trouble, though.

mentioned in merge request !10 (merged)

mentioned in commit ecfed6fc

mentioned in commit 89370f46

After more work on the E2E stuff, I've realized that we shouldn't add it to the CI (see last comment for explanation)

closed

mentioned in commit d1a3c581