Test your Capybara knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What does a typical Capybara feature test for a login flow conceptually verify, from start to finish?
Questions in this quiz
What does a typical Capybara feature test for a login flow conceptually verify, from start to finish?
What is a realistic tradeoff to weigh when deciding how much of a test suite should consist of full Capybara feature tests versus narrower unit/controller tests?
What is a general principle Capybara's design illustrates about balancing test realism against test speed/complexity in browser-based testing generally?
When might a test need to switch to a JavaScript-capable driver (like Selenium or a headless Chrome-based driver) instead of Capybara's default Rack::Test driver?
Why might a Capybara test that passes reliably when run alone occasionally fail intermittently ("flaky") when run as part of a larger, parallelized test suite?
Why might a test suite using Capybara's default `Rack::Test` driver run significantly faster than one using a full browser driver like Selenium?
What is a Capybara "driver," and what role does it play in how tests actually execute?
What does Capybara's DSL method `visit` do, e.g. `visit '/login'`?
What do Capybara methods like `click_button`, `fill_in`, and `click_link` collectively enable a test to do?
What is a "headless" browser (like headless Chrome, commonly used with a driver such as Cuprite or Selenium's headless mode) in the context of running Capybara tests, and why is it commonly used in CI?
What is a common testing anti-pattern that Capybara's automatic waiting is specifically meant to help avoid?
What does Capybara's automatic "waiting" behavior (built into finder methods like `find` or assertions like `have_content`) address?