cucumber-in-the-yard 1.6.1 → 1.6.3

metadata

@@ -1,12 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: cucumber-in-the-yard
 version: !ruby/object:Gem::Version 
+  hash: 9
   prerelease: false
   segments: 
   - 1
   - 6
-  - 1
-  version: 1.6.1
+  - 3
+  version: 1.6.3
 platform: ruby
 authors: 
 - Franklin Webber
@@ -14,16 +15,18 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-11-04 00:00:00 -07:00
+date: 2010-11-08 00:00:00 -08:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: gherkin
   prerelease: false
   requirement: &id001 !ruby/object:Gem::Requirement 
+    none: false
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
+        hash: 21
         segments: 
         - 2
         - 2
@@ -35,9 +38,11 @@ dependencies:
   name: cucumber
   prerelease: false
   requirement: &id002 !ruby/object:Gem::Requirement 
+    none: false
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
+        hash: 9
         segments: 
         - 0
         - 7
@@ -49,9 +54,11 @@ dependencies:
   name: yard
   prerelease: false
   requirement: &id003 !ruby/object:Gem::Requirement 
+    none: false
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
+        hash: 5
         segments: 
         - 0
         - 6
@@ -69,22 +76,22 @@ extra_rdoc_files:
 - README.md
 - History.txt
 files: 
-- .autotest
 - .rspec
 - History.txt
 - README.md
 - Rakefile
-- autotest/discover.rb
 - city.gemspec
+- example/child_feature/grandchild_feature/scenario.feature
+- example/child_feature/scenario.feature
 - example/empty.feature
-- example/example.third.feature
-- example/first_example.feature
-- example/second_example.feature
+- example/scenario.feature
+- example/scenario_outline.feature
 - example/step_definitions/example.step.rb
+- example/step_definitions/first.step.rb
 - example/step_definitions/support/env.rb
 - example/step_definitions/support/env_support.rb
 - example/step_definitions/support/support.rb
-- example/sub_features/second_example.feature
+- example/transform.feature
 - lib/city.rb
 - lib/cucumber/city_builder.rb
 - lib/templates/default/feature/html/background.erb
@@ -98,6 +105,8 @@ files:
 - lib/templates/default/feature/setup.rb
 - lib/templates/default/featuredirectory/html/directory.erb
 - lib/templates/default/featuredirectory/html/setup.rb
+- lib/templates/default/featuretags/html/namespace.erb
+- lib/templates/default/featuretags/html/setup.rb
 - lib/templates/default/fulldoc/html/css/common.css
 - lib/templates/default/fulldoc/html/full_list.erb
 - lib/templates/default/fulldoc/html/full_list_features.erb
@@ -115,13 +124,12 @@ files:
 - lib/templates/default/scenario/setup.rb
 - lib/templates/default/steptransformers/html/steptransformers.erb
 - lib/templates/default/steptransformers/html/transformers.erb
+- lib/templates/default/steptransformers/html/undefined_steps.erb
 - lib/templates/default/steptransformers/setup.rb
 - lib/templates/default/tag/html/feature.erb
 - lib/templates/default/tag/html/scenario.erb
 - lib/templates/default/tag/html/tag.erb
 - lib/templates/default/tag/setup.rb
-- lib/templates/default/tags/html/namespace.erb
-- lib/templates/default/tags/html/setup.rb
 - lib/yard/code_objects/cucumber/base.rb
 - lib/yard/code_objects/cucumber/feature.rb
 - lib/yard/code_objects/cucumber/namespace_object.rb
@@ -132,6 +140,7 @@ files:
 - lib/yard/code_objects/namespace_object.rb
 - lib/yard/code_objects/step_definition.rb
 - lib/yard/code_objects/step_transform.rb
+- lib/yard/code_objects/step_transformer.rb
 - lib/yard/handlers/cucumber/base.rb
 - lib/yard/handlers/cucumber/feature_handler.rb
 - lib/yard/handlers/step_definition_handler.rb
@@ -140,14 +149,6 @@ files:
 - lib/yard/parser/source_parser.rb
 - lib/yard/rake/city_task.rb
 - lib/yard/templates/helpers/base_helper.rb
-- spec/city/feature_parser_spec_examples.rb
-- spec/city/gherkin_loader_spec.rb
-- spec/city/test.feature
-- spec/city/yard_handlers_cucumber_spec.rb
-- spec/city/yard_namespace_object_spec.rb
-- spec/city/yard_parser_cucumber_spec.rb
-- spec/city/yard_rb_extensions_spec.rb
-- spec/spec_helper.rb
 has_rdoc: true
 homepage: http://github.com/burtlo/Cucumber-In-The-Yard
 licenses: []
@@ -156,11 +157,11 @@ post_install_message: |+
   
   (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::)
   
-    Thank you for installing Cucumber-In-The-YARD 1.6.1 / 2010-11-04.
+    Thank you for installing Cucumber-In-The-YARD 1.6.3 / 2010-11-08.
     
     Changes:
       
-    * FIX - Feature Directries with sub-directories aborted serialization
+    * FIX Step Definitions and Step Transforms incorrectly cached the YARD Constants
     
   
   (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::)
@@ -170,23 +171,27 @@ rdoc_options:
 require_paths: 
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement 
+  none: false
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      hash: 3
       segments: 
       - 0
       version: "0"
 required_rubygems_version: !ruby/object:Gem::Requirement 
+  none: false
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      hash: 3
       segments: 
       - 0
       version: "0"
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.3.6
+rubygems_version: 1.3.7
 signing_key: 
 specification_version: 3
 summary: Cucumber Features in YARD

data/.autotest

@@ -1,15 +0,0 @@
-require 'autotest/growl'
-
-Autotest.add_hook :initialize do |at|
-  #%w{ features definitions common browser jmx }.each {|exception| at.add_exception(exception)}
-end
-
-# Overrides to include the required folders to make this project autotestable
-# This is because requires cannot exist within the options file
-class Autotest::Rspec < Autotest
-  def make_test_cmd(files_to_test)
-    files_to_test.empty? ? '' :
-      "#{ruby} #{SPEC_PROGRAM} -r lib/city.rb --color --autospec #{normalize(files_to_test).keys.flatten.join(' ')} #{add_options_if_present}"
-  end
-end
-

data/autotest/discover.rb

@@ -1,3 +0,0 @@
-#./autotest/discover.rb
-
-Autotest.add_discovery { "rspec2" }

data/example/example.third.feature

@@ -1,33 +0,0 @@
-@customer
-Feature: Customer Account
-  As a customer of the product I am able to configure settings for my account
-
-  Background:
-    Given this third defined step definition
-	And the customer has the following details:
-      | Name  | Email       | Age |
-      | Roger | r@email.com | 22  |
-
-  @bvt
-  Scenario: Customer is able to change their password
-    Given that a customer that is logged in to the system
-    When the customer changes their password to 'lions_tigers_and_bears'
-    Then I expect when they login again that it will use this new password
-
-  @wip
-  Scenario: Customer cannot change settings if they are not logged in
-    Given that a customer is a valid customer
-    When the customer visits the account settings page
-    Then I expect the customer to be presented with the login page
-	
-  @wip
-  Scenario: Customer cannot change settings if they are not logged in
-    Given that a customer that is logged in to the system
-	When the customer visits the account settings page
-	And edits their the biography to state:
-	"""
-		I am an avid golfer, spelunker, and designer of clothing for stuffed
-		animals.
-	"""
-    Then I expect the customer to be presented with the login page
-

data/example/first_example.feature

@@ -1,19 +0,0 @@
-@feature @bvt
-Feature: Feature File
-  As a product owner it is important for me to be able to view a feature file through
-  an interface which is easily accessible.  A feature's description appears along side
-  the comments for the feature.
-
-  Background:
-    Given this first background step
-
-  @bvt
-  Scenario: First Scenario
-    Given this first scenario step
-    When this is parsed with Cucumber-In-The-YARD
-    Then I expect that each step is highlighted and matched to a step definition 
-
-  Scenario: Second Scenario
-    Given this first scenario step
-    When this is parsed with Cucumber-In-The-YARD
-    Then I expect that this scenario is present

data/example/second_example.feature

@@ -1,51 +0,0 @@
-@customer
-Feature: Customer Logout Feature
-  As a customer of the product I am able to logout
-
-  Background:
-    Given this undefined step definition
-
-  @bvt @param2 @param3
-  Scenario: Customer that is logged in is able to log out
-    Given that a customer is a valid customer
-    And a customer logs in as username 'frank' with password 'default'
-    And I expect them to have logged in successfully
-    When the customer logs out
-	Then I expect the customer to be shown the logout page
-
-  Scenario: Customers with a complete profile are allowed to post
-    Given that a customer is a valid customer
-    And the customer has the following details:
-      | Name  | Email       | Age |
-      | Roger | r@email.com | 22  |
-	And the customer has the following details:
-      | Name  | Email       | Age |
-      | Roger | r@email.com | 22  |
-    When a customer logs in as username 'frank' with password 'default'
-	And visits the customer update page
-	Then I expect the customer is able able to post to their profile
-
-  @optional_parameters
-  Scenario: Optional Parameter Step Definition
-    # This step definition has some optional parameters
-    Given a project
-    And an inactive project
-    And a project with the name 'optional', start date 10/26/2010, nicknamed 'norman'
-
-  @highlighting
-  Scenario: Highlighting
-    Given a duck that has a bill
-    Then I expect the duck to quack
-
-  @product
-  Scenario Outline: Customers that bought a product are included in their product groups
-    Given that <Customer> is a valid customer
-    And that the product, named '<Product>', is a valid product
-    When the customer has purchased the product
-    Then I expect the customer to be a member of the '<Product>' group
-
-    Examples:
-     | Customer   | Product   |
-     | Customer A | Product A |
-     | Customer A | Product B |
-     | Customer A | Product C |

data/example/sub_features/second_example.feature

@@ -1,51 +0,0 @@
-@customer
-Feature: Customer Logout Feature
-  As a customer of the product I am able to logout
-
-  Background:
-    Given this undefined step definition
-
-  @bvt @param2 @param3
-  Scenario: Customer that is logged in is able to log out
-    Given that a customer is a valid customer
-    And a customer logs in as username 'frank' with password 'default'
-    And I expect them to have logged in successfully
-    When the customer logs out
-	Then I expect the customer to be shown the logout page
-
-  Scenario: Customers with a complete profile are allowed to post
-    Given that a customer is a valid customer
-    And the customer has the following details:
-      | Name  | Email       | Age |
-      | Roger | r@email.com | 22  |
-	And the customer has the following details:
-      | Name  | Email       | Age |
-      | Roger | r@email.com | 22  |
-    When a customer logs in as username 'frank' with password 'default'
-	And visits the customer update page
-	Then I expect the customer is able able to post to their profile
-
-  @optional_parameters
-  Scenario: Optional Parameter Step Definition
-    # This step definition has some optional parameters
-    Given a project
-    And an inactive project
-    And a project with the name 'optional', start date 10/26/2010, nicknamed 'norman'
-
-  @highlighting
-  Scenario: Highlighting
-    Given a duck that has a bill
-    Then I expect the duck to quack
-
-  @product
-  Scenario Outline: Customers that bought a product are included in their product groups
-    Given that <Customer> is a valid customer
-    And that the product, named '<Product>', is a valid product
-    When the customer has purchased the product
-    Then I expect the customer to be a member of the '<Product>' group
-
-    Examples:
-     | Customer   | Product   |
-     | Customer A | Product A |
-     | Customer A | Product B |
-     | Customer A | Product C |

data/spec/city/feature_parser_spec_examples.rb

@@ -1,153 +0,0 @@
-
-shared_examples_for "a feature file" do
-  it "should have a defined feature" do
-    @parser.features.first.should_not be_nil
-  end
-
-  it "the feature should have a unique name" do
-    @parser.features.first.name.should == @feature[:file].gsub('.','_').to_sym
-  end
-
-  it "the feature should have the specified title" do
-    @parser.features.first.value.should == @feature[:name]
-  end
-
-  it "the feature should have all specified tags" do
-    @feature[:tags].find do |expected_tag|
-      @parser.features.first.tags.find{|tag| tag.value == expected_tag }
-    end.should_not be_nil
-  end
-  
-  it "the feature should have the correct number of tags" do
-    @feature[:tags].each do |expected_tag|
-      @parser.features.first.tags.find_all {|tag| tag.value == expected_tag }.count.should == 1
-    end
-  end
-  
-  it "the feature's tags should have a file" do
-    @parser.features.first.tags.each do |tag|
-      tag.files.should_not be_nil
-      tag.files.should_not be_empty
-      tag.files.first.first.should == @feature[:file]
-    end
-  end
-
-  it "the feature should have a description" do
-    @parser.features.first.description.join("\n") == @feature[:description].join("\n")
-  end
-
-  it "the feature should have a file" do 
-    @parser.features.first.files.first[0].should == @feature[:file]
-  end
-
-  it "the feature should have a line number" do
-    @parser.features.first.files.first[1].should_not be_nil
-  end
-
-end
-
-shared_examples_for "a feature file with a background" do
-
-  it "the feature should have a background" do
-    @parser.features.first.background.should_not be_nil
-  end
-
-  it "the background should have a unique scenario name" do
-    @parser.features.first.background.name.should == "#{@feature[:file]}.background".gsub('.','_').to_sym
-  end
-
-  it "the background should have the correct title" do
-    @parser.features.first.background.value.should == "Background"  
-  end
-
-  it "the background should have a file" do
-    @parser.features.first.background.files.first[0].should == @feature[:file]
-  end
-
-  it "the background should have a line number" do
-    @parser.features.first.background.files.first[1].should_not be_nil
-  end
-
-  it "the background should have all their defined steps" do
-    @parser.features.first.scenarios.first.steps.should_not be_nil
-    if @background
-      @background.each_with_index do |step,index|
-        @parser.features.first.background.steps[index].value.should == step
-      end
-    end
-  end
-  
-  it "the background steps should have files and line numbers" do
-    if @background
-      @background.each_with_index do |step,index|
-        @parser.features.first.background.steps[index].files.first[0].should == @feature[:file]
-        @parser.features.first.background.steps[index].files.first[1].should_not be_nil
-      end
-    end
-  end
-
-end
-
-shared_examples_for "a feature file with scenarios" do
-  it "should have all scenarios" do
-    @scenarios.each_with_index do |scenario,index|
-      @parser.features.first.scenarios[index].should_not be_nil  
-    end
-  end
-
-  it "each scenario should have a unique scenario name" do
-    @parser.features.first.scenarios.first.name.should == "#{@feature[:file]}_scenario_0".gsub('.','_').to_sym
-  end
-
-  it "each scenario should have the correct title" do
-    @parser.features.first.scenarios.each_with_index do |scenario,index|
-      scenario.value.should == @scenarios[index][:title].join("\n")
-    end  
-  end
-
-  it "each scenario should have the correct tags" do
-    @scenarios.each_with_index do |scenario,index|
-      scenario[:tags].each do |expeced_tag|
-        @parser.features.first.scenarios[index].tags.find {|tag| tag.value == expeced_tag}.should_not be_nil
-      end
-    end
-  end
-
-  it "each scenario should have the correct number of tags" do
-    @parser.features.first.scenarios.first.tags.find_all {|tag| tag.value == "@ninja" }.count.should == 1
-  end
-
-  it "each scenario should have a file" do
-    @parser.features.first.scenarios.first.files.first[0].should == @feature[:file]
-  end
-
-  it "each scenario should have a line number" do
-    @parser.features.first.scenarios.first.files.first[1].should_not be_nil
-  end
-
-  it "each scenario should have all their defined steps" do
-    @parser.features.first.scenarios.first.steps.should_not be_nil
-    if @scenarios
-      @scenarios.each_with_index do |scenario,scenario_index|
-        @parser.features.first.scenarios[scenario_index].should_not be_nil
-
-        scenario[:steps].each_with_index do |step,step_index|
-          @parser.features.first.scenarios[scenario_index].steps[step_index].name.should == "#{@feature[:file].gsub('.','_')}_scenario_#{scenario_index}_step_#{step_index}".to_sym
-          @parser.features.first.scenarios[scenario_index].steps[step_index].value.should == step
-        end
-      end
-    end
-  end
-
-  it "each scenario's steps should have files and line numbers" do
-    if @scenarios
-      @scenarios.each_with_index do |scenario,scenario_index|
-        scenario[:steps].each_with_index do |step,step_index|
-          @parser.features.first.scenarios[scenario_index].steps[step_index].files.first[0].should == @feature[:file]
-          @parser.features.first.scenarios[scenario_index].steps[step_index].files.first[1].should_not be_nil
-        end
-      end
-    end
-  end
-  
-end

data/spec/city/gherkin_loader_spec.rb

@@ -1,39 +0,0 @@
-require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')
-
-describe "Gherkin" do
-
-
-  before(:all) do
-    
-    @source = File.dirname(__FILE__) + '/test.feature'
-    File.should exist(@source)
-    @data = File.open(@source, 'r').read
-    
-    @parser = YARD::Parser::Cucumber::FeatureParser.new(@data,@source)
-  
-  end
-
-
-  it "should not be nil" do
-    @parser.should_not be_nil
-  end
-
-  it "should parse" do
-    @parser.parse
-  end
-  
-  it "should tokenize" do
-    @parser.tokenize
-  end
-  
-  it "should enumerator" do
-    @parser.enumerator
-  end
-    
-
-
-
-
-
-
-end

data/spec/city/test.feature

@@ -1,36 +0,0 @@
-@customer
-Feature: Customer Logout Feature
-  As a customer of the product I am able to logout
-
-  Background:
-    Given this undefined step definition
-
-  @bvt
-  Scenario: Customer that is logged in is able to log out
-    Given that a customer is a valid customer
-    And a customer logs in as username 'frank' with password 'default'
-    And I expect them to have logged in successfully
-    When the customer logs out
-	Then I expect the customer to be shown the logout page
-
-  Scenario: Customers with a complete profile are allowed to post
-    Given that a customer is a valid customer
-    And the customer has the following details:
-      | Name  | Email       | Age |
-      | Frank | f@email.com | 22  | 
-    When a customer logs in as username 'frank' with password 'default'
-	And visits the customer update page
-	Then I expect the customer is able able to post to their profile
-	
-  @product
-  Scenario Outline: Customers that bought a product are included in their product groups
-    Given that <Customer> is a valid customer
-    And that the product, named '<Product>', is a valid product
-    When the customer has purchased the product
-    Then I expect the customer to be a member of the '<Product>' group
-
-    Examples:
-     | Customer   | Product   |
-     | Customer A | Product A |
-     | Customer A | Product B |
-     | Customer A | Product C |

data/spec/city/yard_handlers_cucumber_spec.rb

@@ -1,24 +0,0 @@
-require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')
-
-module YARD::Handlers::Cucumber
-
-  describe Base do
-    
-    it "should respond to method handles?" do
-      Base.should respond_to(:handles?)
-    end
-    
-  end
-  
-  describe FeatureHandler do
-    
-    it "should respond to method process" do
-      FeatureHandler.should respond_to(:process)  
-    end
-    
-  end
-  
-  
-  
-  
-end

data/spec/city/yard_namespace_object_spec.rb

@@ -1,8 +0,0 @@
-require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')
-
-module YARD::CodeObjects
-
-  describe NamespaceObject do
-  end
-
-end