Rails%203%20In%20Action

270 CHAPTER 10 Tracking state
You’ll start out by writing a feature to create new states, which will involve creating
a new controller called Admin::StatesController. This controller will provide the
admins of your application with the basic CRUD functionality for states, as well as the
ability to mark a state as the default, which all tickets will then be associated with.
We’re not going to look at adding an edit, update, or destroy action to this controller
because it’s been covered previously and should be left as an exercise for you.
10.4.1 Adding additional states
You have three default states from the db/seeds.rb file currently: New, Open, and
Closed. If the admin users of your application wish to add more, they can’t—not until
you’ve created the Admin::StatesController and the new and create actions inside
it. This will allow those users to create additional states which then can be assigned to
a ticket.
You have this lovely State model, but no way for admins of the application to add
any new records to it. What if they want to add more states? You’ll create a new controller
called Admin::StatesController and put a new and create action in it so that
admins can create more states.
But before you write any real code, you’ll write a feature that describes the process
of creating a state. Put it in a new file called features/creating_states.feature, which is
shown in the following listing.
Listing 10.21 features/creating_states.feature
Feature: Creating states
In order to be able to specify other states for tickets
As an admin
I want to add them to the application
Background:
Given there are the following users:
| email | password | admin |
| admin@ticketee.com | password | true |
And I am signed in as them
Scenario: Creating a state
When I follow "Admin"
And I follow "States"
And I follow "New State"
And I fill in "Name" with "Duplicate"
And I press "Create State"
Then I should see "State has been created."
Here you sign in as an admin user and go through the motions of creating a new state.
When you run this feature through using the command bin/cucumber features/
creating_states.feature, it will fail because it can’t find the States link:
And I follow "States"
no link with title, id or text 'States' found (Capybara::ElementNotFound)