mirage 1.3.6 → 2.0.0.alpha1

data/features/client/get.feature

@@ -1,46 +0,0 @@
-Feature: the Mirage client provides a method for getting responses
-  There is no need to escape any parameters before using the client api as this is done for you.
-
-  Background:
-    Given the following gems are required to run the Mirage client test code:
-    """
-    require 'rubygems'
-    require 'rspec'
-    require 'mirage'
-    """
-    And I post to 'http://localhost:7001/mirage/set/greeting' with parameters:
-      | response | hello |
-
-  Scenario: getting a response
-    Given I run
-    """
-    Mirage::Client.new.get('greeting').should == 'hello'
-    """
-
-  Scenario: getting a response with parameters
-    Given I run
-    """
-    Mirage::Client.new.get('greeting', :firstname => 'leon', :surname => 'davis').should == 'hello'
-    """
-    And I hit 'http://localhost:7001/mirage/track/1'
-    Then 'firstname=leon&surname=davis' should be returned
-
-  Scenario: getting a response with a request body
-    Given I run
-    """
-    Mirage::Client.new.get('greeting','<greetingRequest></greetingRequest>').should == 'hello'
-    """
-    And I hit 'http://localhost:7001/mirage/track/1'
-    Then '<greetingRequest></greetingRequest>' should be returned
-
-  Scenario: getting a response that does not exist
-    Given I run
-    """
-    begin
-      Mirage::Client.new.get('response_that_does_not_exits').should == 'hello'
-      fail("Error should have been thrown")
-    rescue Exception => e
-      e.is_a?(Mirage::ResponseNotFound).should == true
-    end
-    """
-

data/features/server/file_responses.feature

@@ -1,8 +0,0 @@
-Feature: Mirage can also be used to host files.
-
-  Scenario: A file is set as a response
-    Given I hit 'http://localhost:7001/mirage/set/some/location/download' with parameters:
-      | response | README.md |
-
-    When I hit 'http://localhost:7001/mirage/get/some/location/download'
-    Then the response should be a file the same as 'README.md'

data/features/server/track.feature

@@ -1,74 +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 hit 'http://localhost:7001/mirage/set/greeting' with parameters:
-      | response | Hello |
-
-
-  Scenario: Tracking a response that was triggered by a request that had content in the body
-    Given I hit 'http://localhost:7001/mirage/get/greeting' with request body:
-    """
-    Hello MockServer
-    """
-    When I hit 'http://localhost:7001/mirage/track/1'
-    Then 'Hello MockServer' should be returned
-
-
-  Scenario: Tracking a response that was triggered by a request with a query string
-    Given I hit 'http://localhost:7001/mirage/get/greeting' with parameters:
-      | surname   | Davis |
-      | firstname | Leon  |
-    When I hit 'http://localhost:7001/mirage/track/1'
-    Then 'surname=Davis&firstname=Leon' should be returned
-
-
-  Scenario: Tracking a response that has not been served yet
-    Given I hit 'http://localhost:7001/mirage/track/1'
-    Then a 404 should be returned
-
-
-  Scenario: A response is peeked at
-    Given I hit 'http://localhost:7001/mirage/get/greeting' with request body:
-    """
-    Hello
-    """
-    And I hit 'http://localhost:7001/mirage/peek/1'
-    When I hit 'http://localhost:7001/mirage/track/1'
-    Then 'Hello' should be returned
-
-
-  Scenario: A default response and one for the same endpoint with a pattern are set
-    When I hit 'http://localhost:7001/mirage/set/greeting' with parameters:
-      | response | Hello who ever you are |
-    Then '1' should be returned
-
-    When I hit 'http://localhost:7001/mirage/set/greeting' with parameters:
-      | response | Hello Leon |
-      | pattern  | Leon       |
-    Then '3' should be returned
-
-    When I hit 'http://localhost:7001/mirage/get/greeting' with request body:
-    """
-    My name is Joel
-    """
-    And I hit 'http://localhost:7001/mirage/get/greeting' with request body:
-    """
-    My name is Leon
-    """
-    And I hit 'http://localhost:7001/mirage/track/1'
-    Then 'My name is Joel' should be returned
-    And I hit 'http://localhost:7001/mirage/track/3'
-    Then 'My name is Leon' should be returned
-
-