Rails%203%20In%20Action

10.2.4 Seeding states
Changing a ticket’s state
If you add some states to the db/seeds.rb file, users will be able to select them from the
State drop-down box on the tickets page rather than leaving it blank and useless,
much like it is now. With these states in the db/seeds.rb file, as mentioned before, you
will have a repeatable way of creating this data if you ever need to run your application
on another server, such as would be the case when you put the application on another
computer.
You’re adding these files to the db/seeds.rb so you have some to play around with
in the development environment of your application. You’re attempting to figure out
why, when a user picks Open from the State select box and clicks Create Comment,
the state doesn’t display on the ticket that should be updated.
When you go to the Ticketee Beta project to create a ticket and then attempt to create
a comment on that ticket with the state of Open, you’ll see that there are no states
(as shown in figure 10.7).
You should add a couple of states to your seeds file now; they’ll
be New, Open, and Closed. Ideally, New will be the default state of
tickets, and you’ll set this up a little later on. Before adding these
states, let’s add a couple of steps to features/seed.feature to always
ensure that your states are defined.
You extend this feature to go inside the Ticketee Beta project,
create a ticket, and then begin to create a comment on that ticket. When it’s on the
comment-creation screen, you check to see that all your states are in the state box. To
do this, modify the scenario in this file to what’s shown in the following listing.
Listing 10.14 features/seed.feature, the basics scenario
Scenario: The basics
Given I have run the seed task
And I am signed in as "admin@ticketee.com"
When I follow "Ticketee Beta"
And I follow "New Ticket"
And I fill in "Title" with "Comments with state"
And I fill in "Description" with "Comments always have a state."
And I press "Create Ticket"
Then I should see "New" within "#comment_state_id"
And I should see "Open" within "#comment_state_id"
And I should see "Closed" within "#comment_state_id"
The #comment_state_id element referenced here is the State select box for your comments,
and you’re confirming that it’s got the three states you’re going to be seeding
your database with. When you run this feature by running bin/cucumber features/
seed.feature, it will fail because you don’t have your states yet:
Then I should see "New" within "#comment_state_id"
is not true. (Test::Unit::AssertionFailedError)
Let’s add these states to your db/seeds.rb file by using the lines shown in the following
listing.
259
Figure 10.7
Oops! No states!