mirage 2.4.2 → 3.0.0.alpha.1

data/features/server/templates/put/put_as_default.feature

@@ -1,42 +0,0 @@
-Feature: A template can be configure as the default response for when there is no response found for a sub url.
-  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 send PUT to 'http://localhost:7001/mirage/templates/level0/level1' with body 'another level'
-    Given I send PUT to 'http://localhost:7001/mirage/templates/level1' with body 'level 1' and headers:
-      | X-mirage-default | true |
-    
-    When I send GET to 'http://localhost:7001/mirage/responses/level1/level2'
-    Then 'level 1' should be returned
-
-
-  Scenario: More than one potential default response exists
-    Given I send PUT to 'http://localhost:7001/mirage/templates/level1' with body 'level 1' and headers:
-      | X-mirage-default | true |
-    Given I send PUT to 'http://localhost:7001/mirage/templates/level1/level2' with body 'level 2' and headers:
-      | X-mirage-default | true |
-    Given I send PUT to 'http://localhost:7001/mirage/templates/level1/level2/level3' with body 'level 3' and headers:
-      | X-mirage-default | false |
-    Given I send PUT to 'http://localhost:7001/mirage/templates/level1/level2/level3/level4' with body 'level 4' and headers:
-      | X-mirage-pattern | a pattern that wont be matched |
-    Given I send PUT to 'http://localhost:7001/mirage/templates/leve11/level2/level3/level4/level5' with body 'level 5' and headers:
-      | X-mirage-default | true |
-
-    When I send GET to 'http://localhost:7001/mirage/responses/level1/level2/level3/level4'
-    Then 'level 2' should be returned
-
-
-  Scenario: There isnt a default response
-    Given I send PUT to 'http://localhost:7001/mirage/templates/level1' with body 'level 1'
-    When I send GET to 'http://localhost:7001/mirage/responses/level1/level2'
-    Then a 404 should be returned

data/features/server/templates/put/put_with_delay.feature

@@ -1,8 +0,0 @@
-Feature: Its possible introduce a delay before responding to a client with a particular response. This lets you simulate real world
-  conditions by making your application wait before receiving a response.
-
-  Scenario: Response with a delay
-    Given I send PUT to 'http://localhost:7001/mirage/templates/an_appology' with body 'Sorry' and headers:
-    | X-mirage-delay | 4.2 |
-    When I send GET to 'http://localhost:7001/mirage/responses/an_appology'
-    Then it should take at least '4.2' seconds

data/features/server/templates/put/put_with_pattern.feature

@@ -1,80 +0,0 @@
-Feature: Mirage can be configured to return particular responses conditionally based on if a prescribed pattern is found in
-  querystring or the body of a request.
-
-  Patterns can be either plain text or a regular expression
-
-  A response with a pattern is not considered the same a response at the same address that has either no pattern or a diffferent one.
-  This allows you to specify different behaviour depending on the request.
-
-  Background: There is already a default response for 'greeting'
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello Stranger' and headers:
-      | X-mirage-method | POST |
-
-  Scenario: A plain text pattern found in the request body
-
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello Leon, how are you?' and headers:
-      | X-mirage-pattern | <name>leon</name> |
-      | X-mirage-method  | POST              |
-    When I send POST to 'http://localhost:7001/mirage/responses/greeting' with request entity
-    """
-     <greetingRequest>
-      <name>leon</name>
-     </greetingRequest>
-    """
-    Then 'Hello Leon, how are you?' should be returned
-
-
-  Scenario: A regex based pattern found in the request body
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello Leon, how are you?' and headers:
-      | X-mirage-pattern | .*?leon<\/name> |
-      | X-mirage-method  | POST            |
-    When I send POST to 'http://localhost:7001/mirage/responses/greeting' with request entity
-    """
-     <greetingRequest>
-      <name>leon</name>
-     </greetingRequest>
-    """
-    Then 'Hello Leon, how are you?' should be returned
-
-
-  Scenario: A plain text pattern found in the query string
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello Leon, how are you?' and headers:
-      | X-mirage-pattern | leon |
-      | X-mirage-method  | POST |
-    When I send POST to 'http://localhost:7001/mirage/responses/greeting' with parameters:
-      | name | leon |
-    Then 'Hello Leon, how are you?' should be returned
-
-
-  Scenario:  A regex based pattern found in the query string
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello Leon, how are you?' and headers:
-      | X-mirage-pattern | name=[L\|l]eon |
-      | X-mirage-method  | POST           |
-    When I send POST to 'http://localhost:7001/mirage/responses/greeting' with parameters:
-      | name | leon |
-
-    Then 'Hello Leon, how are you?' should be returned
-
-
-  Scenario: The pattern is not matched
-    Given I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello Leon, how are you?' and headers:
-      | X-mirage-pattern | .*?leon<\/name> |
-      | X-mirage-method  | POST            |
-    When I send POST to 'http://localhost:7001/mirage/responses/greeting' with request entity
-    """
-     <greetingRequest>
-      <name>jim</name>
-     </greetingRequest>
-    """
-
-    Then 'Hello Stranger' should be returned
-
-  Scenario: Templates with different patterns on the same address
-    When I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello Leon, how are you?' and headers:
-      | X-mirage-pattern | 2 |
-
-    When I send PUT to 'http://localhost:7001/mirage/templates/greeting' with body 'Hello Leon, how are you?' and headers:
-      | X-mirage-pattern | 3 |
-    Then '3' should be returned
-    
-      

data/lib/mirage/client/response.rb

@@ -1,29 +0,0 @@
-require 'ostruct'
-module Mirage
-  class Response
-
-    attr_accessor :content_type,:method, :pattern, :default, :status, :delay
-    attr_reader :value
-
-    def initialize response
-      @content_type = 'text/plain'
-      @value = response
-      @method = :get
-      @status = 200
-      @delay = 0
-    end
-
-    def headers
-      headers = {}
-      headers['Content-Type']=@content_type
-      headers['X-mirage-file'] = 'true' if @response.kind_of?(IO)
-      headers['X-mirage-method'] = @method
-      headers['X-mirage-pattern'] = @pattern if @pattern
-      headers['X-mirage-default'] = @default if @default == true
-      headers['X-mirage-status'] = @status
-      headers['X-mirage-delay'] = @delay
-      headers
-    end
-
-  end
-end

data/spec/client_spec.rb

@@ -1,38 +0,0 @@
-require 'spec_helper'
-require 'mirage/client'
-
-
-
-describe Mirage::Client do
-  include Mirage
-
-  before :each do
-    @response = mock('response').as_null_object
-  end
-
-
-  it 'is configured to connect to local host port 7001 by default' do
-    client = Client.new
-    client.should_receive(:http_put).with(/localhost:7001/, anything, anything).and_return(@response)
-    client.put "greeting", "hello"
-  end
-
-  it 'can be configured with a url pointing to Mirage' do
-    url = "http://url.for.mirage"
-    client = Client.new url
-    client.should_receive(:http_put).with(/#{url}/, anything, anything).and_return(@response)
-    client.put "greeting", "hello"
-  end
-
-  it 'can be configured with a port refering to which port Mirage is running on on localhost' do
-    port = 9001
-    client = Client.new :port => port
-    client.should_receive(:http_put).with(/localhost:#{port}/, anything, anything).and_return(@response)
-    client.put "greeting", "hello"
-  end
-
-  it 'raises an error if neither a port or url specified in the argument' do
-    expect{Client.new({})}.should raise_error()
-    expect{Client.new("rubbish")}.should raise_error()
-  end
-end

data/views/index.erb

@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html
-        PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-<head>
-    <title>Mirage</title>
-</head>
-<body>
-<h1>Welcome to Mirage</h1>
-
-<p>Below are any responses you are currently hosting. Click the response itself to peek at it and click 'track' to view the last request that triggered it.<br/> 
-    <br/>
-    Patterns and delays are shown for responses that have them.<br/>
-    <br/>
-    Responses with '*' at the end are default responses. I.e. they will be returned, where appropriate, for requests to a sub endpoint if a response is not found at that level.<br/>
-    <br/>
-    <strong>Note:</strong> if requests or responses contain xml, you will need to view page source to see it properly.</p>
-
-<% unless @responses.empty? %>
-<table border="1" width='100%'>
-    <% @responses.each do |key, response| %>
-        <tr><td><a id='peek_response_<%=response.response_id%>' href="/mirage/templates/<%=response.response_id%>"><%=key%></a></td><td><a id='track_response_<%=response.response_id%>' href="/mirage/requests/<%=response.response_id%>">track</a></td></tr>
-    <% end %>
-</table>
-<% end %>
-</body>
-</html>