Quick and easy browser testing using RSpec and Rails 5.1
summary
Claims that full-stack browser tests "just work" on modern RSpec and Rails with concrete details: RSpec 3.7 hooks into Rails 5.1 system specs and defaults to driven_by :selenium (Chrome), offers a non-JS rack_test path, requires Puma tuned to threads 0,1 workers 0 for correct server threading, and writes failure screenshots (renderable in iTerm2). Integration lands and runs, had a few real-world bugs fixed, and Rails 5.2 compatibility requires a tiny patch.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:25Quick and easy browser testing using RSpec and Rails 5.1
- 3:15It's cool when rails versions get released
- 4:04Rails has changed
- 5:45Let's talk about testing
- 8:48Just google "rails browser testing"
- 19:38Implementation
- 21:12Rails does the heavy lifting
- 21:34Let's talk about screenshots
- 28:47Open source is imperfect
- 30:46Recording and Production Confreaks
related talks
28mTeaching RSpec to Play nice with Rails
31mSecrets of Testing Rails 5 Apps
49mFront End Testing Frontier
35mFrom RSpec to Jest: JavaScript testing for Rails devs
36mBuilding the Rails ActionDispatch::SystemTestCase framework
01h 19mBDD and Acceptance Testing with RSpec & Capybara
35mFrom RSpec to Jest: JavaScript testing for Rails devs
41mJavascript TDD for Rubyists