In this screencast, we do a sad path to illustrate features of Cucumber because it is able to use existing code. The first step on line 5 of Figure 7.8 passes but the step on line 6 fails because we haven’t modified index.html.haml to include name of new page or include a form for typing in a movie to search for. We fix this by adding this form to index.html.haml, using same Rails methods described in Sections 3.12 and 3.14 of Chapter 3. When creating a form, we have to specify which controller action will receive it; we chose the name search_tmdb for controller action. (We’ll implement this method in the next chapter). Once we have updated index.html.haml and named the controller action, Cucumber colors the steps on lines 5 to 7 green. The next step on line 8 fails. Even though we specified name of controller action, there is no route that would match an incoming URI to the name. To keep things simple, we will set up a route just for that action in config/routes.rb, again using techniques discussed in Section 3.9 of Chapter 3.