before running bundle install.
Also, do NOT add chromedriver-helper to your Gemfile as recommended by the book.The gem is obsolete, you should already have the appropriate chromedriver installed on your PC.
Run unit and integration tests. All tests should pass.
Find an RSpec unit test and break an expectation. See what happens when you re-run the test.
Find an RSpec feature test and break an expectation. See what happens when you re-run the test.
Your first E2E feature
Write a feature test for CRUDing movies in your MovieDB application.
Use Capybara to talk to the simulated browser.
Unit vs. Feature testing
Add the following feature to MovieDB:
Above the movies list is a text field and a button "Search"
When the user enters text into the text field and hits "Search", the movies index is filtered to only contain matching movies
Some hints for the implementation:
Your Movie model should gain a class method Movie.search(query) or even better a scope method you can apply to the scope in the controller. Why should this not be an instance method?
You can implement the search in either SQL or Ruby
The form_for helper is not helpful for the search form above the index. Why is that so? What can you use instead?
Add a custom route /movies/search to your routes, and map it to a new #search action in MoviesController
Try to reuse some of the existing private methods for the implementation of #search
When rendering search results, try to reuse the existing index views, or at least large parts of its.
Now add tests for both the new method Movie.search() and the new UI.