Use cypress for integration tests #6646
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cc @himdel @chessbyte
This PR is a basic POC of writing integration tests with cypress.
I chose cypress because I like how it doesn't use selenium/phantomjs, but instead spins up a real headless browser and interacts with it directly. The tooling for it is really good with a live interactive UI with time travel and DOM selector discovery, CLI support, screenshot generation on failure, video generation of the run, and a lot more. It only supports Chrome (and Chromium/Canary/Electron) right now, but they are very close to getting Firefox. Even so, for 1st tier testing Chrome should be more than good enough.
Running the tests
In a separate tab, run
bundle exec rails server
, then...Running the interactive tool
npm run cypress:open