mirage 3.0.13 → 3.0.14

data/features/client/configure.feature

@@ -1,72 +0,0 @@
-Feature: Configuring Templates
-
-  If you find yourself setting the same basic http settings for templates, the client can be configured to preset these.
-
-  Background:
-    Given the following require statements are needed:
-    """
-    require 'rubygems'
-    require 'rspec/expectations'
-    require 'mirage/client'
-    """
-
-  Scenario: configuring the client on instance
-    Given I run
-    """
-    client = Mirage::Client.new do
-      http_method :post
-      status 202
-      default true
-      delay 2
-      content_type "text/xml"
-    end
-
-    client.put('greeting','hello')
-    """
-    When POST is sent to '/responses/greeting/for/someone'
-    Then 'hello' should be returned
-    And a 202 should be returned
-    Then it should take at least '2' seconds
-    And the response 'content-type' should be 'text/xml'
-
-  Scenario: Configuring a client after it has been created
-    Given I run
-    """
-    client = Mirage::Client.new
-    client.configure do
-      http_method :post
-      status 202
-      default false
-      delay 2
-      content_type "text/xml"
-    end
-
-    client.put('greeting','hello')
-    """
-    When POST is sent to '/responses/greeting'
-    Then 'hello' should be returned
-    And a 202 should be returned
-    Then it should take at least '2' seconds
-    And the response 'content-type' should be 'text/xml'
-
-  Scenario: resetting defaults
-    Given I run
-    """
-    client = Mirage::Client.new
-    client.configure do
-      http_method :post
-      status 202
-      default true
-      delay 2
-      content_type "text/xml"
-    end
-
-    client.reset
-    client.put('greeting','hello')
-    """
-    When GET is sent to '/responses/greeting'
-    Then 'hello' should be returned
-
-
-
-

data/features/client/model.feature

@@ -1,95 +0,0 @@
-Feature: Template Models
-
-  Use Models to for an object oriented approach to defining Templates.
-
-  The Mirage client provides the Mirage::Template::Model module that can be used to define your own model classes.
-
-  Having extended this module you must provide a 'body' method to customise the body of the response
-
-  The Model module provides class level methods for:
-
-  * Defaulting characteristics such as HTTP status code and Content-type
-
-  * Defining instance level methods that can set and get values.
-
-  Instances of classes that extend this module will also have all of the standard methods of a Mirage Template and hence you can also set your request requirements directly on them too.
-
-  Any defaults set using methods provided  can be overridden after instances are created and when the client is used to add them as Templates to Mirage. See below for examples.
-
-
-  Background:
-    Given the following require statements are needed:
-    """
-    require 'rubygems'
-    require 'mirage/client'
-    """
-
-
-  Scenario: Defining a Model
-    Given I run
-    """
-      class UserProfile
-        extend Mirage::Template::Model
-
-        endpoint '/users'
-        http_method :get
-        status 202
-        content_type 'text/html'
-
-        def body
-          "Joe Blogs"
-        end
-      end
-
-      Mirage::Client.new.put UserProfile.new
-    """
-    When GET is sent to '/responses/users'
-    Then 'Joe Blogs' should be returned
-    And a 202 should be returned
-    And the content-type should be 'text/html'
-
-
-  Scenario: Defining builder methods
-    Given I run
-    """
-      class UserProfile
-        extend Mirage::Template::Model
-        endpoint '/users'
-
-        builder_methods :firstname, :surname
-
-        def body
-          "#{firstname} #{surname}"
-        end
-      end
-
-      Mirage::Client.new.put UserProfile.new.firstname('Joe').surname('Blogs')
-    """
-    When GET is sent to '/responses/users'
-    Then 'Joe Blogs' should be returned
-
-  Scenario: Overriding model defaults
-    Given I run
-    """
-      class UserProfile
-        extend Mirage::Template::Model
-        endpoint '/users'
-
-        builder_methods :firstname, :surname
-        status '200'
-
-        def body
-          "Joe Blogs"
-        end
-      end
-
-      Mirage::Client.new.put '/profiles', UserProfile.new do
-        status 202
-      end
-    """
-    When GET is sent to '/responses/profiles'
-    Then 'Joe Blogs' should be returned
-    And a 202 should be returned
-
-
-

data/features/client/preview_responses.feature

@@ -1,33 +0,0 @@
-Feature: Inspecting Templates
-
-  The client can be used to retrieve a template stored on Mirage.
-
-  Background:
-    Given the following require statements are needed:
-    """
-    require 'rubygems'
-    require 'rspec/expectations'
-    require 'mirage/client'
-    """
-
-  Scenario: retrieving a Template
-    Given a template for 'greeting' has been set with a value of 'Hello'
-
-    When I run
-    """
-      Mirage::Client.new.templates(1).body.should == 'Hello'
-    """
-
-    When GET is sent to '/requests/1'
-    Then a 404 should be returned
-
-  Scenario: retrieving a Template that does not exist
-    Given I run
-    """
-    begin
-      Mirage::Client.new.templates(2).should == 'this should not have happened'
-      fail("Error should have been thrown")
-    rescue Exception => e
-      e.is_a?(Mirage::TemplateNotFound).should == true
-    end
-    """

data/features/client/prime.feature

@@ -1,32 +0,0 @@
-Feature: Priming Mirage
-
-  The client can be used to prime Mirage with Templates found in the templates directory that was configured when Mirage was started.
-
-  Background:
-    Given the following require statements are needed:
-    """
-    require 'rubygems'
-    require 'rspec/expectations'
-    require 'mirage/client'
-    """
-
-  Scenario: Priming Mirage
-    Given Mirage is not running
-    And I run 'mirage start'
-
-    When the file 'mirage/default_greetings.rb' contains:
-    """
-    prime do |mirage|
-      mirage.put('greeting', 'hello')
-      mirage.put('leaving', 'goodbye')
-    end
-    """
-    And I run
-    """
-    Mirage::Client.new.prime
-    """
-    And GET is sent to '/responses/greeting'
-    Then 'hello' should be returned
-
-    When GET is sent to '/responses/leaving'
-    Then 'goodbye' should be returned

data/features/client/put.feature

@@ -1,111 +0,0 @@
-Feature: Adding Templates
-
-  The Mirage client provides methods for setting Templates.
-
-  The client will escape all data for you so your free to just get on with using Mirage :)
-
-  Body, Header, and Parameter requirements can be specified as either a String or Regexp
-
-  Background:
-    Given the following require statements are needed:
-    """
-    require 'rubygems'
-    require 'rspec/expectations'
-    require 'mirage/client'
-    """
-
-
-  Scenario: Setting a Template on Mirage
-    Given I run
-    """
-    Mirage::Client.new.put('greeting','hello')
-    """
-    When GET is sent to '/responses/greeting'
-    Then 'hello' should be returned
-
-  Scenario: Setting the required HTTP method
-    Given I run
-    """
-    Mirage::Client.new.put('greeting', 'Hello Leon') do
-      http_method 'POST'
-    end
-    """
-    When GET is sent to '/responses/greeting'
-    Then a 404 should be returned
-    When POST is sent to '/responses/greeting'
-    Then 'Hello Leon' should be returned
-
-
-  Scenario: Setting a requirement on body content
-    Given I run
-    """
-    Mirage::Client.new.put('greeting', 'Hello Leon') do
-      http_method 'POST'
-      required_body_content << /leon/
-    end
-    """
-    When POST is sent to '/responses/greeting'
-    Then a 404 should be returned
-    When I send POST to '/responses/greeting' with request entity
-    """
-     <greetingRequest>
-      <name>leon</name>
-     </greetingRequest>
-    """
-    Then 'Hello Leon' should be returned
-
-  Scenario: Setting a requirement on requests parameters
-    Given I run
-    """
-    Mirage::Client.new.put('greeting', 'Hello Leon') do
-      http_method 'POST'
-      required_parameters[:name] = /leon/
-    end
-    """
-    When POST is sent to '/responses/greeting'
-    Then a 404 should be returned
-    When I send POST to '/responses/greeting' with parameters:
-      | name | leon |
-
-    Then 'Hello Leon' should be returned
-
-  Scenario: setting a response as default
-    Given I run
-    """
-    Mirage.start.clear
-
-    Mirage::Client.new.put('greeting', 'default greeting') do
-      default true
-    end
-    """
-    When GET is sent to '/responses/greeting/for/joel'
-    Then 'default greeting' should be returned
-
-
-  Scenario: Setting the content type
-    Given I run
-    """
-    Mirage::Client.new.put('greeting', '<xml></xml>') do
-      content_type 'text/xml'
-    end
-    """
-    When GET is sent to '/responses/greeting'
-    And the response 'content-type' should be 'text/xml'
-
-
-  Scenario: Setting the HTTP status code
-    Given I run
-    """
-    Mirage::Client.new.put('greeting', 'hello'){status 203}
-    """
-    When GET is sent to '/responses/greeting'
-    Then a 203 should be returned
-
-
-  Scenario: Setting a delay
-    Given I run
-    """
-    Mirage::Client.new.put('greeting', 'hello'){delay 2}
-    """
-    When GET is sent to '/responses/greeting'
-    Then it should take at least '2' seconds

data/features/client/readme.md

@@ -1,3 +0,0 @@
-Mirage has a client implemented in Ruby. It's fully functional and includes a command line interface for controlling the Mirage server direct from your test suite.
-
-

data/features/client/requests.feature

@@ -1,20 +0,0 @@
-Feature: Retrieving tracked requests
-
-  Requests made to the Mirage Server can be retrieved using the Mirage client
-
-  Background:
-    Given the following require statements are needed:
-    """
-    require 'rubygems'
-    require 'mirage/client'
-    """
-
-  Scenario: Retrieving request data
-    Given a template for 'greeting' has been set with a value of 'Hello'
-
-    When I send GET to '/responses/greeting' with parameters:
-      | name | leon  |
-    Then I run
-    """
-       Mirage::Client.new.requests(1).parameters.should == {'name' => 'leon'}
-    """

data/features/client/running.feature

@@ -1,51 +0,0 @@
-@command_line
-Feature: How to check if Mirage is running
-
-  Use the Mirage client api to check if Mirage is running either on the local machine or on a remote host.
-
-
-  Background:
-    Given the following require statements are needed:
-    """
-    require 'rubygems'
-    require 'rspec/expectations'
-    require 'mirage/client'
-    """
-
-
-  Scenario: Check if mirage is running on the local machine on the default port
-    Given Mirage is not running
-    Then I run
-    """
-      Mirage.running?.should == false
-    """
-    Given Mirage is running
-    Then I run
-    """
-      Mirage.running?.should == true
-    """
-
-
-  Scenario: Check if mirage is running on the local machine on a non standard port
-    Given I run 'mirage start -p 9001'
-    Then I run
-    """
-      Mirage.running?(:port => 9001).should == true
-    """
-
-
-  Scenario: Checking if mirage is running on remote machine
-    Given I run 'mirage start -p 9001'
-    Then I run
-    """
-      Mirage.running? "http://localhost:9001"
-    """
-
-
-  Scenario: Check if mirage is running using the client directly
-    Given I run 'mirage start -p 9001'
-    Then I run
-    """
-      client = Mirage::Client.new "http://localhost:9001"
-      client.running?.should == true
-    """

data/features/client/save_and_revert.feature

@@ -1,39 +0,0 @@
-Feature: Creating snapshots
-
-  The client can be used to snapshot and rollback the Mirage server
-
-
-  Background:
-    Given the following require statements are needed:
-    """
-    require 'rubygems'
-    require 'rspec/expectations'
-    require 'mirage/client'
-    """
-    And a template for 'greeting' has been set with a value of 'The default greeting'
-
-
-  Scenario: Creating a snapshot and rolling back
-    Given I run
-    """
-    Mirage::Client.new.save
-    """
-    And I send PUT to '/templates/leaving' with request entity
-    """
-    Goodbye
-    """
-
-    And I send PUT to '/templates/greeting' with request entity
-    """
-    Changed
-    """
-
-    When I run
-    """
-    Mirage::Client.new.revert
-    """
-    And GET is sent to '/responses/leaving'
-    Then a 404 should be returned
-
-    When GET is sent to '/responses/greeting'
-    Then 'The default greeting' should be returned