Rails%203%20In%20Action

Given /^I have an account$/ do
@account = Account.new
end
Behavior-driven development
Steps are defined by using regular expressions, which are used when you wish to match
strings. In this case, you’re matching the step in the feature with this step definition by
putting the text after the Given keyword into a regular expression. After the regular
expression is the do Ruby keyword, which matches up with the end at the end. This
syntax indicates a block, and this block is run (“called”) when this step definition is
matched.
With this step defined, you can try running cucumber features/account.feature
to see if the feature will pass. No—it fails with this error:
Given I have an account
uninitialized constant Object::Account (NameError)
Similar to the beginning of the RSpec showcase, create a lib directory inside your
accounts directory. To define this constant, you create a file in this new directory
called account.rb. In this file you put code to define the class, shown in the following
listing.
class Account
end
Listing 2.26 features/step_definitions/account_steps.rb
Listing 2.27 accounts/lib/account.rb
This file is not loaded automatically, of course: you have to require it just as you did in
RSpec with lib/bacon.rb. Cucumber’s authors already thought of this and came up
with a solution. Any file inside of features/support is automatically loaded, with one
special file being loaded before all the others: features/support/env.rb. This file
should be responsible for setting up the foundations for your tests. Now create features/support/env.rb
and put these lines inside it:
$LOAD_PATH