This was the case with this new Rails app, but seeing as we wanted tests to be fully supported in our new CI pipeline, we needed to figure out how to deal with system specs, and by extension, Selenium. Getting JavaScript-enabled system specs working when you run the tests locally isn’t too bad - mostly just install a few gems, configure them per their respective READMEs, and off you go. The first app we’re deploying is a greenfield (yet to be used in production) Rails app which uses RSpec and includes Rails 5.1/6-style “system specs” which use Capybara to drive a web browser. I will update this article as soon as I have time to do so.Īt work, I’ve been spending some time getting our Rails projects deployed on new Kubernetes infrastructure, and we’re taking the opportunity to fix some problems with our current CI pipeline - the biggest of which is a lack of tests. Some specific information on the changes can be found in this Upgrade to Selenium 4 help article, which I followed when I fixed my setup during recent gem & Rails upgrades for an application that uses the method outlined in this article. The changes are mostly trivial but they mean that this guide cannot be followed to the letter for newer versions of these gems.
Note (Mar 8, 2022): Some changes have been made in more recent versions of the Selenium and/or Capybara gems that make certain code in this guide inaccurate, particularly relating to the constructors of the Selenium drivers.
0 kommentar(er)
