Rails%203%20In%20Action

First steps
The render method in this variation renders the app/views/projects/_form.html.erb
partial at this location.
Now, running rake cucumber:ok once more, you can see that your feature is one
step closer to finishing: the field is filled in. How did Capybara know where to find the
correct field to fill in? Simple. When you defined the field inside app/views/projects/
_form.html.erb, you used the syntax shown in the following listing.
Capybara finds the label containing the "Name" text you ask for in your scenario and
fills out the corresponding field. Capybara has a number of ways to locate a field, such
as by the name of the corresponding label, the id attribute of the field, or the name
attribute. The last two look like this:
When I fill in "project_name" with "TextMate 2"
# or
When I fill in "project[name]" with "TextMate 2"
These aren’t human friendly ways to find a field, so let’s use "Name" instead.
When you run the feature again with rake cucumber:ok, you get this error:
And I press "Create Project"
The action 'create' could not be found for ProjectsController
The feature now complains of a missing action called create. To define this action,
you define the create method underneath the new method in the Projects-
Controller, as in the following listing.
def create
@project = Project.new(params[:project])
@project.save
flash[:notice] = "Project has been created."
redirect_to @project
end
The new method takes the argument params, which is available inside controller methods
and returns the parameters passed to the action, such as those from the form, as a
HashWithIndifferentAccess object. These are different from normal Hash objects,
because you can reference a String key by using a matching Symbol and vice versa. In
this case, the params hash is
{
Listing 3.16 app/views/projects/_form.html.erb
Listing 3.17 app/controllers/projects_controller.rb
"commit" => "Create Project",
"action" => "create",
"project" => {
"name" => "TextMate 2"
67