Rails%203%20In%20Action

First steps
Listing 3.25 features/creating_projects.feature
Scenario: Creating a project without a name
Given I am on the homepage
When I follow "New Project"
And I press "Create Project"
Then I should see "Project has not been created."
And I should see "Name can't be blank"
The first two steps are identical to the ones you placed inside the other scenario. You
should eliminate this duplication by making pour code DRY (Don’t Repeat Yourself!).
This is another term you’ll hear a lot in the Ruby world. It’s easy to extract common
code from where it’s being duplicated and into a method or a module you can use
instead of the duplication. One line of code is 100 times better than 100 lines of duplicated
code. To DRY up your code, before the first scenario, you define a background.
For Cucumber, backgrounds have a layout identical to scenarios but are executed
before every scenario inside the feature. Delete the two steps from the top of both of
these scenarios so that they now look like the following listing.
Listing 3.26 features/creating_projects.feature
Scenario: Creating a project
And I fill in "Name" with "TextMate 2"
And I press "Create Project"
Then I should see "Project has been created."
And I should be on the project page for "TextMate 2"
And I should see "TextMate 2 - Projects - Ticketee"
Scenario: Creating a project without a name
And I press "Create Project"
Then I should see "Project has not been created."
And I should see "Name can't be blank"
Then on the line before the first Scenario, define the Background, as in the next listing.
Listing 3.27 features/creating_projects.feature
Background:
Given I am on the homepage
When I follow "New Project"
Now when you run rake cucumber:ok, this will fail because it cannot see the error
message on the page:
Then I should see "Project has not been created."
To get this feature to do what you want it to do, add a validation. Validations are
defined on the model and typically are run before the data is put into the database,
but this can be made optional, as you’ll see later. To define a validation ensuring the
name attribute is there, open the app/models/project.rb file and make it look like the
following listing.
77