We need to decide if we want to go with CapybaraWebkit/QT or headless CapybaraSelenium/ChromeDriver for javascript tests. The former apparently runs faster, but I speak from experience when I say QT can be a real pain in the ass to install on macos, and can break with xcode updates. The latter is slightly slower, but significantly easier to install. It also does not have the benefit of getting to watch an automated browser do its thing, but then it's also not focus-stealing which is nice.
This was done on my old Tinder rails app, so we can reference basic structure there.
We need to decide if we want to go with CapybaraWebkit/QT or headless CapybaraSelenium/ChromeDriver for javascript tests. The former apparently runs faster, but I speak from experience when I say QT can be a real pain in the ass to install on macos, and can break with xcode updates. The latter is slightly slower, but significantly easier to install. It also does not have the benefit of getting to watch an automated browser do its thing, but then it's also not focus-stealing which is nice.
This was done on my old Tinder rails app, so we can reference basic structure there.
More info:
https://robots.thoughtbot.com/headless-feature-specs-with-chrome?utm_source=rubyweekly&utm_medium=email