mirage 0.1.4 → 0.1.5

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    mirage (0.1.4)
+    mirage (0.1.5)
       mechanize (>= 1.0.0)
       rack (~> 1.1.0)
       ramaze (>= 2011.01.30)
@@ -19,16 +19,12 @@ GEM
     diff-lcs (1.1.2)
     gherkin (2.3.5)
       json (>= 1.4.6)
-    gherkin (2.3.5-java)
-      json (>= 1.4.6)
     innate (2011.01)
       rack (>= 1.1.0)
     json (1.5.1)
-    json (1.5.1-java)
     mechanize (1.0.0)
       nokogiri (>= 1.2.1)
-    nokogiri (1.4.4-java)
-      weakling (>= 0.0.3)
+    nokogiri (1.4.4)
     rack (1.1.2)
     rake (0.8.7)
     ramaze (2011.01.30)
@@ -42,10 +38,8 @@ GEM
       diff-lcs (~> 1.1.2)
     rspec-mocks (2.5.0)
     term-ansicolor (1.0.5)
-    weakling (0.0.4-java)
 
 PLATFORMS
-  java
   ruby
 
 DEPENDENCIES

data/bin/mirage

@@ -31,7 +31,7 @@ if ARGV.include?('start')
 
   start_mirage(ARGV, mirage_client)
   begin
-    mirage_client.load_defaults
+    mirage_client.prime
   rescue Mirage::InternalServerException => e
     puts "WARN: #{e.message}"
   end

data/features/client/setting_responses.feature

@@ -32,20 +32,20 @@ Feature: the Mirage client provides methods for setting responses and loading de
     """
     Then 'Hello Leon' should be returned
 
-  Scenario: Loading default responses
+  Scenario: Priming Mirage
     Given Mirage is not running
     And I run 'mirage start'
 
-    When the file 'defaults/default_greetings.rb' contains:
+    When the file 'responses/default_greetings.rb' contains:
     """
-    Mirage.default do |mirage|
+    Mirage.prime do |mirage|
       mirage.set('greeting', :response => 'hello')
       mirage.set('leaving', :response => 'goodbye')
     end
     """
     And I run
     """
-    Mirage::Client.new.load_defaults
+    Mirage::Client.new.prime
     """
     And I hit 'http://localhost:7001/mirage/get/greeting'
     Then 'hello' should be returned
@@ -54,15 +54,15 @@ Feature: the Mirage client provides methods for setting responses and loading de
     Then 'goodbye' should be returned
 
 
-  Scenario: Setting defaults and one of the files has something bad in it
-    Given the file 'defaults/default_greetings.rb' contains:
+  Scenario: Priming Mirage when one of the response file has something bad in it
+    Given the file 'responses/default_greetings.rb' contains:
     """
     Something bad...
     """
     When I run
     """
     begin
-      Mirage::Client.new.load_defaults
+      Mirage::Client.new.prime
       fail("Error should have been thrown")
     rescue Exception => e
       e.is_a?(Mirage::InternalServerException).should == true

data/features/default_responses.feature

@@ -1,91 +1,48 @@
-@command_line
-Feature: Mirage can be primed with a default responses.
-  By default, Mirage loads any rb files found in ./defaults on startup. Mirage can also be made to load default responses
-  from a directory of your choosing.
-
-  Defaults can also be added/reloaded after Mirage has started
-
-
-  Scenario: Mirage is started with defaults in the standard location.
-    Given the file 'defaults/default_greetings.rb' contains:
-    """
-    Mirage.default do |mirage|
-      mirage.set('greeting', :response => 'hello')
-      mirage.set('leaving', :response => 'goodbye')
-    end
-    """
-    And I run 'mirage start'
-    When I hit 'http://localhost:7001/mirage/get/greeting'
-    Then 'hello' should be returned
-    When I hit 'http://localhost:7001/mirage/get/leaving'
-    Then 'goodbye' should be returned
-
-
-  Scenario: Mirage is started pointing with a relative path for default responses
-    Given the file './custom_default_location/default_greetings.rb' contains:
-    """
-    Mirage.default do |mirage|
-      mirage.set('greeting', :response => 'hello')
-    end
-    """
-    And I run 'mirage start -d ./custom_default_location'
-    When I hit 'http://localhost:7001/mirage/get/greeting'
-    Then 'hello' should be returned
-
-
-  Scenario: Mirage is started pointing with a full path for default responses
-    Given the file '/tmp/defaults/default_greetings.rb' contains:
-    """
-    Mirage.default do |mirage|
-      mirage.set('greeting', :response => 'hello')
-    end
-    """
-    And I run 'mirage start -d /tmp/defaults'
-    When I hit 'http://localhost:7001/mirage/load_defaults'
-    And I hit 'http://localhost:7001/mirage/get/greeting'
-    Then 'hello' should be returned
-
-
-  Scenario: Reloading default responses after mirage has been started
-    Given the file 'defaults/default_greetings.rb' contains:
-    """
-    Mirage.default do |mirage|
-      mirage.set('greeting', :response => 'hello')
-    end
-    """
-    And I run 'mirage start'
-    And I hit 'http://localhost:7001/mirage/clear'
-    And I hit 'http://localhost:7001/mirage/set/a_new_response' with parameters:
-      | response | new response |
-
-    When I hit 'http://localhost:7001/mirage/load_defaults'
-    When I hit 'http://localhost:7001/mirage/get/greeting'
-    Then 'hello' should be returned
-    When I hit 'http://localhost:7001/mirage/get/a_new_response'
-    Then a 404 should be returned
-
-
-  Scenario: Mirage is started with a bad defaults file
-    Given the file 'defaults/default_greetings.rb' contains:
-    """
-    A file with a mistake in it
-    """
-    When I run 'mirage start'
-    Then I should see 'WARN: Unable to load default responses from: defaults/default_greetings.rb' on the command line
-
-
-  Scenario: Defaults with a mistake in them are reloaded after mirage has been started
-    Given I run 'mirage start'
-    When the file 'defaults/default_greetings.rb' contains:
-    """
-    A file with a mistake in it
-    """
-    And I hit 'http://localhost:7001/mirage/load_defaults'
-    Then a 500 should be returned
-
-
-
-
-
-
-
+Feature: Mirage can respond with a 'default' response when a when the response requested at a sub url is not found.
+  I.e.
+  if a response is held for 'level1' and request comes in for 'level1/level2' the response for 'level1'
+  can be returned if nothing is held for 'level1/level2'
+
+  If a request is made and there is more than one response that could be appropriate then the closet is chosen.
+
+  E.g.
+  responses exist for: 'level1' and 'level1/level2'. If a response for 'level1/level2/level3 is made, then the response for
+  'level1/level2' will be returned as it is the most specific match out of the two.
+
+  Root responses can cause unexpected behaviour and so in order to qualify as a default reponse a client must knowingly mark it as one.
+
+  Scenario: A default response is returned
+    Given I hit 'http://localhost:7001/mirage/set/level0/level1' with parameters:
+      | response | another level |
+    And I hit 'http://localhost:7001/mirage/set/level1' with parameters:
+      | response      | level 1 |
+      | root_response | true    |
+
+    When I hit 'http://localhost:7001/mirage/get/level1/level2'
+    Then 'level 1' should be returned
+
+
+  Scenario: More than one potential default response exists
+    Given I hit 'http://localhost:7001/mirage/set/level1' with parameters:
+      | response      | level 1 |
+      | root_response | true    |
+    And I hit 'http://localhost:7001/mirage/set/level1/level2' with parameters:
+      | response      | level 2 |
+      | root_response | true    |
+    And I hit 'http://localhost:7001/mirage/set/level1/level2/level3' with parameters:
+      | response | level 3 |
+    And I hit 'http://localhost:7001/mirage/set/level1/level2/level3/level4' with parameters:
+      | pattern | a pattern that wont be matched |
+    And I hit 'http://localhost:7001/mirage/set/level1/level2/level3/level4/level5' with parameters:
+      | response      | level 5 |
+      | root_response | true    |
+
+    When I hit 'http://localhost:7001/mirage/get/level1/level2/level3/level4'
+    Then 'level 2' should be returned
+
+
+  Scenario: There isnt a default response
+    Given I hit 'http://localhost:7001/mirage/set/level1' with parameters:
+      | response | level 1 |
+    When I hit 'http://localhost:7001/mirage/get/level1/level2'
+    Then a 404 should be returned

data/features/priming.feature

@@ -0,0 +1,93 @@
+@command_line
+Feature: Mirage can be primed with a set of responses.
+  By default, Mirage loads any rb files found in ./responses on startup. Mirage can also be made to load response for a directory
+  of your choosing
+
+  Responses can be added to the responses directory and used to prime Mirage after Mirage has been started.
+  
+  Priming mirage causes any modifications to its state to be lost
+
+
+  Scenario: Mirage is started with the responses to be used for priming located in ./responses
+    Given the file 'responses/default_greetings.rb' contains:
+    """
+    Mirage.prime do |mirage|
+      mirage.set('greeting', :response => 'hello')
+      mirage.set('leaving', :response => 'goodbye')
+    end
+    """
+    And I run 'mirage start'
+    When I hit 'http://localhost:7001/mirage/get/greeting'
+    Then 'hello' should be returned
+    When I hit 'http://localhost:7001/mirage/get/leaving'
+    Then 'goodbye' should be returned
+
+
+  Scenario: Mirage is started pointing with a relative path given for the responses directory
+    Given the file './custom_responses_location/default_greetings.rb' contains:
+    """
+    Mirage.prime do |mirage|
+      mirage.set('greeting', :response => 'hello')
+    end
+    """
+    And I run 'mirage start -d ./custom_responses_location'
+    When I hit 'http://localhost:7001/mirage/get/greeting'
+    Then 'hello' should be returned
+
+
+  Scenario: Mirage is started pointing with a full path for the responses
+    Given the file '/tmp/responses/default_greetings.rb' contains:
+    """
+    Mirage.prime do |mirage|
+      mirage.set('greeting', :response => 'hello')
+    end
+    """
+    And I run 'mirage start -d /tmp/responses'
+    When I hit 'http://localhost:7001/mirage/primes'
+    And I hit 'http://localhost:7001/mirage/get/greeting'
+    Then 'hello' should be returned
+
+
+  Scenario: Priming mirage after its state has been modified
+    Given the file 'responses/default_greetings.rb' contains:
+    """
+    Mirage.prime do |mirage|
+      mirage.set('greeting', :response => 'hello')
+    end
+    """
+    And I run 'mirage start'
+    And I hit 'http://localhost:7001/mirage/clear'
+    And I hit 'http://localhost:7001/mirage/set/a_new_response' with parameters:
+      | response | new response |
+
+    When I hit 'http://localhost:7001/mirage/prime'
+    When I hit 'http://localhost:7001/mirage/get/greeting'
+    Then 'hello' should be returned
+    When I hit 'http://localhost:7001/mirage/get/a_new_response'
+    Then a 404 should be returned
+
+
+  Scenario: Mirage is started with a bad file
+    Given the file 'responses/default_greetings.rb' contains:
+    """
+    A file with a mistake in it
+    """
+    When I run 'mirage start'
+    Then I should see 'WARN: Unable to load default responses from: responses/default_greetings.rb' on the command line
+
+
+  Scenario: Mirage is primed with a bad file after it has been started
+    Given I run 'mirage start'
+    When the file 'responses/default_greetings.rb' contains:
+    """
+    A file with a mistake in it
+    """
+    And I hit 'http://localhost:7001/mirage/prime'
+    Then a 500 should be returned
+
+
+
+
+
+
+

data/features/support/env.rb

@@ -80,7 +80,7 @@ Before do
     start_mirage
   end
   
-  `ls #{SCRATCH}/ | grep -v mirage.log | rm -rf`
+  `cd #{SCRATCH}/ && ls | grep -v mirage.log | xargs rm -rf`
   `truncate -s 0 #{SCRATCH}/mirage.log`
 end
 

data/lib/mirage.rb

@@ -4,7 +4,7 @@ require 'mirage/core'
 require 'mirage/client'
 
 module Mirage
-  def self.default
+  def self.prime
     yield @@client
   end
 

data/lib/mirage/client.rb

@@ -117,8 +117,8 @@ module Mirage
     end
 
     # Clear down the Mirage Server and load any defaults that are in Mirages default responses directory.
-    def load_defaults
-      response(http_post("#{@url}/load_defaults"))
+    def prime
+      response(http_post("#{@url}/prime"))
     end
 
     private

data/lib/mirage/core.rb

@@ -159,7 +159,7 @@ module Mirage
       RESPONSES.clear and RESPONSES.replace(SNAPSHOT.deep_clone)
     end
 
-    def load_defaults
+    def prime
       clear
       Dir["#{DEFAULT_RESPONSES_DIR}/**/*.rb"].each do |default|
         begin

data/lib/mirage/util.rb

@@ -12,7 +12,7 @@ module Mirage
     end
 
     def parse_options args
-      options = {:port => 7001, :defaults_directory => 'defaults', :root_directory => '.'}
+      options = {:port => 7001, :defaults_directory => 'responses', :root_directory => '.'}
 
       opt_parser = OptionParser.new do |opts|
         opts.banner = "Usage: mirage start|stop [options]"

data/mirage.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name = 'mirage'
-  s.version = '0.1.4'
+  s.version = '0.1.5'
   s.authors = ["Leon Davis"]
   s.homepage = 'https://github.com/lashd/mirage'
   s.description = 'Mirage aids testing of your applications by hosting mock responses so that your applications do not have to talk to real endpoints. Its accessible via HTTP and has a RESTful interface.'

metadata

@@ -1,222 +1,199 @@
 --- !ruby/object:Gem::Specification 
 name: mirage
 version: !ruby/object:Gem::Version 
-  prerelease: false
-  segments: 
-    - 0
-    - 1
-    - 4
-  version: 0.1.4
+  prerelease: 
+  version: 0.1.5
 platform: ruby
 authors: 
-  - Leon Davis
+- Leon Davis
 autorequire: 
 bindir: bin
 cert_chain: []
 
-date: 2011-03-25 00:00:00 +00:00
+date: 2011-03-24 00:00:00 +00:00
 default_executable: mirage
 dependencies: 
-  - !ruby/object:Gem::Dependency 
-    name: rack
-    prerelease: false
-    requirement: &id001 !ruby/object:Gem::Requirement 
-      requirements: 
-        - - ~>
-          - !ruby/object:Gem::Version 
-            segments: 
-              - 1
-              - 1
-              - 0
-            version: 1.1.0
-    type: :runtime
-    version_requirements: *id001
-  - !ruby/object:Gem::Dependency 
-    name: ramaze
-    prerelease: false
-    requirement: &id002 !ruby/object:Gem::Requirement 
-      requirements: 
-        - - ">="
-          - !ruby/object:Gem::Version 
-            segments: 
-              - 2011
-              - 1
-              - 30
-            version: 2011.01.30
-    type: :runtime
-    version_requirements: *id002
-  - !ruby/object:Gem::Dependency 
-    name: mechanize
-    prerelease: false
-    requirement: &id003 !ruby/object:Gem::Requirement 
-      requirements: 
-        - - ">="
-          - !ruby/object:Gem::Version 
-            segments: 
-              - 1
-              - 0
-              - 0
-            version: 1.0.0
-    type: :runtime
-    version_requirements: *id003
-  - !ruby/object:Gem::Dependency 
-    name: rake
-    prerelease: false
-    requirement: &id004 !ruby/object:Gem::Requirement 
-      requirements: 
-        - - ">="
-          - !ruby/object:Gem::Version 
-            segments: 
-              - 0
-            version: "0"
-    type: :development
-    version_requirements: *id004
-  - !ruby/object:Gem::Dependency 
-    name: cucumber
-    prerelease: false
-    requirement: &id005 !ruby/object:Gem::Requirement 
-      requirements: 
-        - - ">="
-          - !ruby/object:Gem::Version 
-            segments: 
-              - 0
-            version: "0"
-    type: :development
-    version_requirements: *id005
-  - !ruby/object:Gem::Dependency 
-    name: rspec
-    prerelease: false
-    requirement: &id006 !ruby/object:Gem::Requirement 
-      requirements: 
-        - - ">="
-          - !ruby/object:Gem::Version 
-            segments: 
-              - 0
-            version: "0"
-    type: :development
-    version_requirements: *id006
-  - !ruby/object:Gem::Dependency 
-    name: bundler
-    prerelease: false
-    requirement: &id007 !ruby/object:Gem::Requirement 
-      requirements: 
-        - - ">="
-          - !ruby/object:Gem::Version 
-            segments: 
-              - 0
-            version: "0"
-    type: :development
-    version_requirements: *id007
+- !ruby/object:Gem::Dependency 
+  name: rack
+  prerelease: false
+  requirement: &id001 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ~>
+      - !ruby/object:Gem::Version 
+        version: 1.1.0
+  type: :runtime
+  version_requirements: *id001
+- !ruby/object:Gem::Dependency 
+  name: ramaze
+  prerelease: false
+  requirement: &id002 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: 2011.01.30
+  type: :runtime
+  version_requirements: *id002
+- !ruby/object:Gem::Dependency 
+  name: mechanize
+  prerelease: false
+  requirement: &id003 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: 1.0.0
+  type: :runtime
+  version_requirements: *id003
+- !ruby/object:Gem::Dependency 
+  name: rake
+  prerelease: false
+  requirement: &id004 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: "0"
+  type: :development
+  version_requirements: *id004
+- !ruby/object:Gem::Dependency 
+  name: cucumber
+  prerelease: false
+  requirement: &id005 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: "0"
+  type: :development
+  version_requirements: *id005
+- !ruby/object:Gem::Dependency 
+  name: rspec
+  prerelease: false
+  requirement: &id006 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: "0"
+  type: :development
+  version_requirements: *id006
+- !ruby/object:Gem::Dependency 
+  name: bundler
+  prerelease: false
+  requirement: &id007 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: "0"
+  type: :development
+  version_requirements: *id007
 description: Mirage aids testing of your applications by hosting mock responses so that your applications do not have to talk to real endpoints. Its accessible via HTTP and has a RESTful interface.
 email: 
 executables: 
-  - mirage
+- mirage
 extensions: []
 
 extra_rdoc_files: []
 
 files: 
-  - .rvmrc
-  - Gemfile
-  - Gemfile.lock
-  - README.md
-  - bin/mirage
-  - features/checking_for_requests.feature
-  - features/clearing_requests_and_responses.feature
-  - features/client/checking_for_requests.feature
-  - features/client/clearing_responses.feature
-  - features/client/getting_responses.feature
-  - features/client/mirage_client.feature
-  - features/client/peeking.feature
-  - features/client/setting_responses.feature
-  - features/client/snapshotting.feature
-  - features/command_line_iterface.feature
-  - features/default_responses.feature
-  - features/file_hosting.feature
-  - features/logging.feature
-  - features/peeking_at_response.feature
-  - features/resources/test.zip
-  - features/response_templates.feature
-  - features/root_responses.feature
-  - features/setting_responses.feature
-  - features/setting_responses_with_a_delay.feature
-  - features/setting_responses_with_pattern_matching.feature
-  - features/snapshotting.feature
-  - features/step_definitions/my_steps.rb
-  - features/support/env.rb
-  - features/web_user_interface.feature
-  - full_build.sh
-  - lib/config.ru
-  - lib/mirage.rb
-  - lib/mirage/client.rb
-  - lib/mirage/core.rb
-  - lib/mirage/util.rb
-  - lib/mirage/web.rb
-  - lib/start_mirage.rb
-  - lib/view/mirage/index.xhtml
-  - mirage.gemspec
-  - rakefile
+- .rvmrc
+- Gemfile
+- Gemfile.lock
+- README.md
+- bin/mirage
+- features/checking_for_requests.feature
+- features/clearing_requests_and_responses.feature
+- features/client/checking_for_requests.feature
+- features/client/clearing_responses.feature
+- features/client/getting_responses.feature
+- features/client/mirage_client.feature
+- features/client/peeking.feature
+- features/client/setting_responses.feature
+- features/client/snapshotting.feature
+- features/command_line_iterface.feature
+- features/default_responses.feature
+- features/file_hosting.feature
+- features/logging.feature
+- features/peeking_at_response.feature
+- features/priming.feature
+- features/resources/test.zip
+- features/response_templates.feature
+- features/setting_responses.feature
+- features/setting_responses_with_a_delay.feature
+- features/setting_responses_with_pattern_matching.feature
+- features/snapshotting.feature
+- features/step_definitions/my_steps.rb
+- features/support/env.rb
+- features/web_user_interface.feature
+- full_build.sh
+- lib/config.ru
+- lib/mirage.rb
+- lib/mirage/client.rb
+- lib/mirage/core.rb
+- lib/mirage/util.rb
+- lib/mirage/web.rb
+- lib/start_mirage.rb
+- lib/view/mirage/index.xhtml
+- mirage.gemspec
+- rakefile
 has_rdoc: true
 homepage: https://github.com/lashd/mirage
 licenses: []
 
-post_install_message: |
-  
-  ===============================================================================
-  Thanks you for installing mirage-0.1.4.   
-  
-  Run Mirage with:
-  
-  mirage start
-  ===============================================================================
-
+post_install_message: "\n\
+  ===============================================================================\n\
+  Thanks you for installing mirage-0.1.5.   \n\n\
+  Run Mirage with:\n\n\
+  mirage start\n\
+  ===============================================================================\n"
 rdoc_options: []
 
 require_paths: 
-  - lib
+- lib
 required_ruby_version: !ruby/object:Gem::Requirement 
+  none: false
   requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        segments: 
-          - 0
-        version: "0"
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
 required_rubygems_version: !ruby/object:Gem::Requirement 
+  none: false
   requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        segments: 
-          - 0
-        version: "0"
+  - - ">="
+    - !ruby/object:Gem::Version 
+      version: "0"
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.3.6
+rubygems_version: 1.6.1
 signing_key: 
 specification_version: 3
-summary: mirage-0.1.4
+summary: mirage-0.1.5
 test_files: 
-  - features/checking_for_requests.feature
-  - features/clearing_requests_and_responses.feature
-  - features/client/checking_for_requests.feature
-  - features/client/clearing_responses.feature
-  - features/client/getting_responses.feature
-  - features/client/mirage_client.feature
-  - features/client/peeking.feature
-  - features/client/setting_responses.feature
-  - features/client/snapshotting.feature
-  - features/command_line_iterface.feature
-  - features/default_responses.feature
-  - features/file_hosting.feature
-  - features/logging.feature
-  - features/peeking_at_response.feature
-  - features/resources/test.zip
-  - features/response_templates.feature
-  - features/root_responses.feature
-  - features/setting_responses.feature
-  - features/setting_responses_with_a_delay.feature
-  - features/setting_responses_with_pattern_matching.feature
-  - features/snapshotting.feature
-  - features/step_definitions/my_steps.rb
-  - features/support/env.rb
-  - features/web_user_interface.feature
+- features/checking_for_requests.feature
+- features/clearing_requests_and_responses.feature
+- features/client/checking_for_requests.feature
+- features/client/clearing_responses.feature
+- features/client/getting_responses.feature
+- features/client/mirage_client.feature
+- features/client/peeking.feature
+- features/client/setting_responses.feature
+- features/client/snapshotting.feature
+- features/command_line_iterface.feature
+- features/default_responses.feature
+- features/file_hosting.feature
+- features/logging.feature
+- features/peeking_at_response.feature
+- features/priming.feature
+- features/resources/test.zip
+- features/response_templates.feature
+- features/setting_responses.feature
+- features/setting_responses_with_a_delay.feature
+- features/setting_responses_with_pattern_matching.feature
+- features/snapshotting.feature
+- features/step_definitions/my_steps.rb
+- features/support/env.rb
+- features/web_user_interface.feature

data/features/root_responses.feature

@@ -1,47 +0,0 @@
-Feature: Mirage can respond with a 'root' response when a when the response requested at a sub url is not found.
-  I.e.
-  if a response is held for 'level1' and request comes in for 'level1/level2' the response for 'level1'
-  can be returned if nothing is held for 'level1/level2'
-
-  If a request is made and there is more than one response that could be appropriate then the closet is chosen.
-
-  E.g.
-  responses exist for: 'level1' and 'level1/level2'. If a response for 'level1/level2/level3 is made, then the response for
-  'level1/level2' will be returned as it is the most specific match out of the two.
-
-  Root responses can cause unexpected behaviour and so in order to qualify as a root reponse a client must knowingly mark it as one.
-
-  Scenario: A root response is returned
-    Given I hit 'http://localhost:7001/mirage/set/level0/level1' with parameters:
-      | response | another level |
-    And I hit 'http://localhost:7001/mirage/set/level1' with parameters:
-      | response      | level 1 |
-      | root_response | true    |
-
-    When I hit 'http://localhost:7001/mirage/get/level1/level2'
-    Then 'level 1' should be returned
-
-
-  Scenario: More than one potential root response exists
-    Given I hit 'http://localhost:7001/mirage/set/level1' with parameters:
-      | response      | level 1 |
-      | root_response | true    |
-    And I hit 'http://localhost:7001/mirage/set/level1/level2' with parameters:
-      | response      | level 2 |
-      | root_response | true    |
-    And I hit 'http://localhost:7001/mirage/set/level1/level2/level3' with parameters:
-      | response      | level 3 |
-      | root_response | false   |
-    And I hit 'http://localhost:7001/mirage/set/level1/level2/level3/level4/level5' with parameters:
-      | response      | level 5 |
-      | root_response | true    |
-
-    When I hit 'http://localhost:7001/mirage/get/level1/level2/level3/level4'
-    Then 'level 2' should be returned
-
-
-  Scenario: There isnt a root response
-    Given I hit 'http://localhost:7001/mirage/set/level1' with parameters:
-      | response | level 1 |
-    When I hit 'http://localhost:7001/mirage/get/level1/level2'
-    Then a 404 should be returned