mirage 2.0.0.alpha3 → 2.0.0.alpha4

metadata

@@ -2,7 +2,7 @@
 name: mirage
 version: !ruby/object:Gem::Version 
   prerelease: 6
-  version: 2.0.0.alpha3
+  version: 2.0.0.alpha4
 platform: ruby
 authors: 
 - Leon Davis
@@ -10,23 +10,12 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-06-08 00:00:00 +01:00
+date: 2011-08-11 00:00:00 +01:00
 default_executable: mirage
 dependencies: 
-- !ruby/object:Gem::Dependency 
-  name: rack
-  requirement: &id001 !ruby/object:Gem::Requirement 
-    none: false
-    requirements: 
-    - - ~>
-      - !ruby/object:Gem::Version 
-        version: 1.1.0
-  type: :runtime
-  prerelease: false
-  version_requirements: *id001
 - !ruby/object:Gem::Dependency 
   name: sinatra
-  requirement: &id002 !ruby/object:Gem::Requirement 
+  requirement: &id001 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ">="
@@ -34,10 +23,10 @@ dependencies:
         version: "0"
   type: :runtime
   prerelease: false
-  version_requirements: *id002
+  version_requirements: *id001
 - !ruby/object:Gem::Dependency 
   name: childprocess
-  requirement: &id003 !ruby/object:Gem::Requirement 
+  requirement: &id002 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -45,21 +34,21 @@ dependencies:
         version: "0.1"
   type: :runtime
   prerelease: false
-  version_requirements: *id003
+  version_requirements: *id002
 - !ruby/object:Gem::Dependency 
   name: rake
-  requirement: &id004 !ruby/object:Gem::Requirement 
+  requirement: &id003 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
-    - - "="
+    - - ">="
       - !ruby/object:Gem::Version 
-        version: 0.9.0
+        version: "0"
   type: :development
   prerelease: false
-  version_requirements: *id004
+  version_requirements: *id003
 - !ruby/object:Gem::Dependency 
   name: cucumber
-  requirement: &id005 !ruby/object:Gem::Requirement 
+  requirement: &id004 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ">="
@@ -67,10 +56,10 @@ dependencies:
         version: "0"
   type: :development
   prerelease: false
-  version_requirements: *id005
+  version_requirements: *id004
 - !ruby/object:Gem::Dependency 
   name: gherkin
-  requirement: &id006 !ruby/object:Gem::Requirement 
+  requirement: &id005 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - "="
@@ -78,10 +67,10 @@ dependencies:
         version: 2.3.9
   type: :development
   prerelease: false
-  version_requirements: *id006
+  version_requirements: *id005
 - !ruby/object:Gem::Dependency 
   name: rspec
-  requirement: &id007 !ruby/object:Gem::Requirement 
+  requirement: &id006 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ">="
@@ -89,10 +78,10 @@ dependencies:
         version: "0"
   type: :development
   prerelease: false
-  version_requirements: *id007
+  version_requirements: *id006
 - !ruby/object:Gem::Dependency 
   name: jeweler
-  requirement: &id008 !ruby/object:Gem::Requirement 
+  requirement: &id007 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ~>
@@ -100,10 +89,10 @@ dependencies:
         version: 1.5.2
   type: :development
   prerelease: false
-  version_requirements: *id008
+  version_requirements: *id007
 - !ruby/object:Gem::Dependency 
   name: bundler
-  requirement: &id009 !ruby/object:Gem::Requirement 
+  requirement: &id008 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ">="
@@ -111,10 +100,10 @@ dependencies:
         version: "0"
   type: :development
   prerelease: false
-  version_requirements: *id009
+  version_requirements: *id008
 - !ruby/object:Gem::Dependency 
   name: sinatra-reloader
-  requirement: &id010 !ruby/object:Gem::Requirement 
+  requirement: &id009 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ">="
@@ -122,10 +111,10 @@ dependencies:
         version: "0"
   type: :development
   prerelease: false
-  version_requirements: *id010
+  version_requirements: *id009
 - !ruby/object:Gem::Dependency 
   name: mechanize
-  requirement: &id011 !ruby/object:Gem::Requirement 
+  requirement: &id010 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ">="
@@ -133,10 +122,10 @@ dependencies:
         version: 1.0.0
   type: :development
   prerelease: false
-  version_requirements: *id011
+  version_requirements: *id010
 - !ruby/object:Gem::Dependency 
   name: gemcutter
-  requirement: &id012 !ruby/object:Gem::Requirement 
+  requirement: &id011 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
     - - ">="
@@ -144,7 +133,7 @@ dependencies:
         version: "0"
   type: :development
   prerelease: false
-  version_requirements: *id012
+  version_requirements: *id011
 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: 
@@ -161,32 +150,33 @@ files:
 - bin/mirage
 - features/client/clear.feature
 - features/client/mirage_client.feature
-- features/client/peek.feature
+- features/client/put.feature
+- features/client/request.feature
+- features/client/response.feature
 - features/client/save_and_revert.feature
-- features/client/set.feature
-- features/client/track.feature
-- features/server/clear.feature
 - features/server/command_line_iterface.feature
 - features/server/logging.feature
-- features/server/peek.feature
 - features/server/prime.feature
-- features/server/response_templates.feature
+- features/server/requests/delete.feature
+- features/server/requests/get.feature
 - features/server/save_and_revert.feature
-- features/server/set.feature
-- features/server/set_default_response.feature
-- features/server/set_with_a_delay.feature
-- features/server/set_with_a_pattern.feature
-- features/server/track_requests.feature
+- features/server/templates/delete.feature
+- features/server/templates/get.feature
+- features/server/templates/put/put.feature
+- features/server/templates/put/put_as_default.feature
+- features/server/templates/put/put_with_delay.feature
+- features/server/templates/put/put_with_pattern.feature
+- features/server/templates/put/put_with_substitutions.feature
 - features/server/web_user_interface.feature
 - features/step_definitions/my_steps.rb
 - features/support/env.rb
 - full_build.sh
-- lib/mirage.rb
 - lib/mirage/client.rb
 - lib/mirage/core.rb
 - lib/mirage/mock_response.rb
 - lib/mirage/mock_responses_collection.rb
 - lib/mirage/object.rb
+- lib/mirage/server.rb
 - lib/mirage/util.rb
 - lib/mirage/web.rb
 - lib/start_mirage.rb
@@ -213,7 +203,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
-      hash: 4414235670568771214
+      hash: -4139461546343420148
       segments: 
       - 0
       version: "0"
@@ -226,7 +216,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.6.1
+rubygems_version: 1.6.2
 signing_key: 
 specification_version: 3
 summary: Mirage is a easy mock server for testing your applications

data/features/server/clear.feature

@@ -1,93 +0,0 @@
-Feature: Responses and requests can be cleared.
-  Clearing a response clears any associated request information that may have been stored.
-
-  Usage:
-  ${mirage_url}/clear - Clear all responses and requests
-  ${mirage_url}/clear/requests - Clear all requests
-  ${mirage_url}/clear/response_id - Clear a requests and response for a particular response
-  ${mirage_url}/clear/request/response_id - Clear request for a particular response
-
-
-  Background: The MockServer has already got a response for greeting and leaving on it.
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello'
-    And I send GET to 'http://localhost:7001/mirage/responses/greeting'
-
-    And I send PUT to 'http://localhost:7001/mirage/templates/leaving' with body 'Goodbye'
-    And I send GET to 'http://localhost:7001/mirage/responses/leaving'
-
-
-  Scenario: Clearing all responses
-    Given I send DELETE to 'http://localhost:7001/mirage/templates'
-
-    When I send GET to 'http://localhost:7001/mirage/requests/1'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/responses/greeting'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/templates/1'
-    Then a 404 should be returned
-
-    When I send GET to 'http://localhost:7001/mirage/requests/2'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/responses/leaving'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/templates/2'
-    Then a 404 should be returned
-
-
-  Scenario: Clearing a particular response
-    Given I send DELETE to 'http://localhost:7001/mirage/templates/1'
-
-    When I send GET to 'http://localhost:7001/mirage/templates/1'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/responses/greeting'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/requests/1'
-    Then a 404 should be returned
-
-    When I send GET to 'http://localhost:7001/mirage/requests/2'
-    Then a 200 should be returned
-    When I send GET to 'http://localhost:7001/mirage/responses/leaving'
-    Then a 200 should be returned
-    When I send GET to 'http://localhost:7001/mirage/templates/2'
-    Then a 200 should be returned
-    
-
-
-  Scenario: Clearing all requests
-    And I send DELETE to 'http://localhost:7001/mirage/requests'
-
-    When I send GET to 'http://localhost:7001/mirage/requests/1'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/responses/greeting'
-    Then a 200 should be returned
-    When I send GET to 'http://localhost:7001/mirage/templates/1'
-    Then a 200 should be returned
-    
-
-    When I send GET to 'http://localhost:7001/mirage/requests/2'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/responses/leaving'
-    Then a 200 should be returned
-    When I send GET to 'http://localhost:7001/mirage/templates/2'
-    Then a 200 should be returned
-    
-
-
-  Scenario: Clearing a stored request for a prticular response
-    And I send DELETE to 'http://localhost:7001/mirage/requests/1'
-    
-    When I send GET to 'http://localhost:7001/mirage/requests/1'
-    Then a 404 should be returned
-    When I send GET to 'http://localhost:7001/mirage/responses/greeting'
-    Then a 200 should be returned
-    When I send GET to 'http://localhost:7001/mirage/templates/1'
-    Then a 200 should be returned
-    
-
-    When I send GET to 'http://localhost:7001/mirage/requests/2'
-    Then a 200 should be returned
-    When I send GET to 'http://localhost:7001/mirage/responses/leaving'
-    Then a 200 should be returned
-    When I send GET to 'http://localhost:7001/mirage/templates/2'
-    Then a 200 should be returned
-    

data/features/server/track_requests.feature

@@ -1,71 +0,0 @@
-Feature: After a response has been served from Mirage, the content of the request that triggered it can be retrieved. This is useful
-  for testing that the correct information was sent to the endpoint.
-
-  On setting a response, a unique id is returned which can be used to look up the last request made to get that response.
-
-  If the the response is reset then the same id is returned in order to make it easier to keep track of.
-
-  Responses hosted on the same endpoint but with a pattern are considered unique and so get their own ID.
-
-  If the request body contains content this is stored. Otherwise it is the query string that is stored.
-
-  If a response is 'peeked' this does not count as a request that should be stored.
-
-  Background: There is a response already on Mirage
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello' and headers:
-      | X-mirage-method | POST |
-
-
-  Scenario: Tracking a response that was triggered by a request that had content in the body
-    Given I send POST to 'http://localhost:7001/mirage/responses/greeting' with request entity
-    """
-    Hello Mirage
-    """
-    When I send GET to 'http://localhost:7001/mirage/requests/1'
-    Then 'Hello Mirage' should be returned
-
-
-  Scenario: Tracking a response that was triggered by a request with a query string
-    Given I send POST to 'http://localhost:7001/mirage/responses/greeting' with parameters:
-      | surname   | Davis |
-      | firstname | Leon  |
-    When I send GET to 'http://localhost:7001/mirage/requests/1'
-    Then 'surname=Davis&firstname=Leon' should be returned
-
-
-  Scenario: Tracking a response that has not been served yet
-    Given I send GET to 'http://localhost:7001/mirage/requests/1'
-    Then a 404 should be returned
-
-
-
-  Scenario: A response is peeked at
-    Given I send POST to 'http://localhost:7001/mirage/responses/greeting' with request entity
-    """
-    Hello
-    """
-    And I send GET to 'http://localhost:7001/mirage/templates/1'
-    When I send GET to 'http://localhost:7001/mirage/requests/1'
-    Then 'Hello' should be returned
-
-
-  Scenario: A default response and one for the same endpoint with a pattern are set
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello who ever you are'
-    Then '2' should be returned
-
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello' and headers:
-      | X-mirage-pattern | Leon |
-    Then '3' should be returned
-
-    When I send GET to 'http://localhost:7001/mirage/responses/greeting' with parameters:
-      | name | Joel |
-    And I send GET to 'http://localhost:7001/mirage/responses/greeting' with parameters:
-      | name | Leon |
-
-    And I send GET to 'http://localhost:7001/mirage/requests/2'
-    Then 'name=Joel' should be returned
-
-    And I send GET to 'http://localhost:7001/mirage/requests/3'
-    Then 'name=Leon' should be returned
-
-

data/lib/mirage.rb

@@ -1,18 +0,0 @@
-require 'mirage/object'
-require 'mirage/web'
-require 'mirage/util'
-require 'mirage/mock_response'
-require 'mirage/mock_responses_collection'
-require 'mirage/core'
-require 'mirage/client'
-
-module Mirage
-  # When mirage starts it loads any ruby files found in the responses directory. Use this method to get hold of a client configured for the running server.
-  def self.prime
-    yield @@client
-  end
-
-  def self.client= client
-    @@client = client
-  end
-end