Rails%203%20In%20Action

260 CHAPTER 10 Tracking state
Listing 10.15 db/seeds.rb
State.create(:name => "New",
:background => "#85FF00",
:color => "white")
State.create(:name => "Open",
:background => "#00CFFD",
:color => "white")
State.create(:name => "Closed",
:background => "black",
:color => "white")
If you try to run rake db:seed now, you see that this task was aborted:
rake aborted!
Validation failed: Email has already been taken
(See full trace by running task with --trace)
When a rake task aborts, it means an exception has been raised. As the output suggests,
you can see the backtrace by running the same command with --trace :rake
db:seed --trace. You’ll now be given the complete backtrace of your rake task and
can determine what broke. The first line of application-related backtrace in the output
provides a useful clue:
/home/you/ticketee/db/seeds.rb:1:in `'
It’s the first line of db/seeds.rb that’s causing the problem! This is the line that creates
your admin user, and it’s rightly failing because you already have a user with the email
address admin@ticketee.com. Let’s comment out these first couple of lines as well as
the line that creates the Ticketee Beta project, because you don’t want two Ticketee
Beta projects. The only line left uncommented in your seeds file should be the line
you’ve just added. When you run rake db:seed again, it will run successfully. Let’s
uncomment these lines that you’ve just commented out.
With these states now defined inside db/seeds.rb, your feature at features/seed
.feature will pass:
1 scenario (1 passed)
10 steps (10 passed)
Also, with your states seeding, you can go back to your
server at http://localhost:3000 and create a comment on
your ticket with any status, because you’re trying to figure
out why the “Creating comments” feature is failing. After
creating your comment, you should see that the ticket’s Figure 10.8 Ugly state output
state doesn’t display as simple text like New, Open, or Closed, but rather as a standard
inspect output, as shown in figure 10.8.
Well, isn’t that ugly and not user-friendly? It flows off the end of the ticket box!
Thankfully, you can fix this by defining the to_s method in your State model to call
the name method: