Rails%203%20In%20Action

210 CHAPTER 8 More authorization
The load method works in a similar fashion to require, loading and executing the
code inside the file. One difference, however, is that load expects the given string (or
Pathname) to be the full path, with the extension, to the file.
First write a feature to ensure that when the seed data is loaded, you can sign in
with the email admin@ticketee.com and the password password and you can get to the
TicketeeBeta project. Put this feature in features/seed.feature, and write it as shown in
the following listing.
Listing 8.21 features/seed.feature
Feature: Seed Data
In order to fill the database with the basics
As the system
I want to run the seed task
Scenario: The basics
Given I have run the seed task
And I am signed in as "admin@ticketee.com"
Then I should see "Ticketee Beta"
It’s a pretty basic feature, but your seed file will be equally basic. Before you create it,
however, you should define the first step of this scenario. You can get the definition
for this step by running bin/cucumber features/seed.feature. The step definition
looks like this:
Given /^I have run the seed task$/ do
pending # express the regexp above with the code you wish you had
end
Put this step definition in a new file called features/step_definitions/
application_steps.rb because it doesn’t really tie in with the other step files you’ve
defined. If you have more steps like this, you can put them into this file later too. The
code for this file is simple:
Given /^I have run the seed task$/ do
load Rails.root + "db/seeds.rb"
end
Now when you run your feature again, it can’t find the user your seed data is supposed
to create:
And I am signed in as "admin@ticketee.com"
Couldn't find User with email = admin@ticketee.com
➥(ActiveRecord::RecordNotFound)
It can’t find this user because you haven’t yet created one for this scenario. This user
should be created by the db/seeds.rbfile. Open this file now, and add a couple of lines
to create this user, set the user up as an admin, and confirm the user, as shown in the
following listing.