Rails%203%20In%20Action

Attaching a file
bottom of features/creating_tickets.feature that creates a ticket with an attachment, 2 as
shown in the following listing.
Listing 9.1 features/creating_tickets.feature
Scenario: Creating a ticket with an attachment
When I fill in "Title" with "Add documentation for blink tag"
And I fill in "Description" with "The blink tag has a speed attribute"
And I attach the file "spec/fixtures/speed.txt" to "File"
And I press "Create Ticket"
B
Attach file
Then I should see "Ticket has been created."
Then I should see "speed.txt" within "#ticket .asset"
In this feature you introduce a new concept: the Attach the File step B of this scenario,
which attaches the file found at the specified path to the specified field. The
path here is deliberately in the spec/fixtures directory because you may use this file for
functional tests later. This directory would usually be used for test fixtures, except that
at the moment, you don’t have any. 3 Create the spec/fixtures/speed.txt file now, and
fill it with some random filler text like this:
The blink tag can blink faster if you use the speed="hyper" attribute.
Try running this feature using bin/cucumber features/creating_tickets.feature
:37 and see how far you get. It fails on the attaching step because the File field isn’t
yet available:
And I attach the file "spec/fixtures/speed.txt" to "File"
cannot attach file, no file field with id, name,
or label 'File' found (Capybara::ElementNotFound)
Add the File field to the ticket form partial directly underneath the p tag for the
description field using the code in the following listing.
Listing 9.2 app/views/tickets/_form.html.erb
You call this field asset internally, but the user will see File. The reason for this is
explained a little later.
In earlier versions of Rails, you were required to specify that this form is multipart.
A multipart form should be used for any HTML form that contains a file-upload field.
In earlier versions, if you didn’t enable this form setting, you’d only get the filename
from the field rather than the file itself. In Rails 3.1, you don’t need to do this because
it’s done automatically if the form uses the file_field. But it’s preferable to indicate
2 Please note that although the blink tag was once a part of HTML, it should never be used. Same goes for the
marquee tag.
3 Nor will you ever, as factories replace them in your application.
215