mirage 3.0.0.alpha.17 → 3.0.0

data/.ruby-gemset

@@ -0,0 +1 @@
+mirage

data/.ruby-version

@@ -0,0 +1 @@
+1.9.3

data/.travis.yml

@@ -0,0 +1,3 @@
+rvm:
+  - '1.9.3'
+  - '2.0.0'

data/Gemfile.lock

@@ -1,104 +1,135 @@
 GEM
   remote: https://rubygems.org/
   specs:
-    backports (2.3.0)
-    bouncy-castle-java (1.5.0146.1)
-    builder (3.0.0)
-    childprocess (0.2.5)
-      ffi (~> 1.0.6)
-    cucumber (1.1.4)
+    addressable (2.3.5)
+    backports (3.3.5)
+    bouncy-castle-java (1.5.0147)
+    builder (3.2.2)
+    childprocess (0.3.9)
+      ffi (~> 1.0, >= 1.0.11)
+    cucumber (1.3.8)
       builder (>= 2.1.2)
-      diff-lcs (>= 1.1.2)
-      gherkin (~> 2.7.1)
-      json (>= 1.4.6)
-      term-ansicolor (>= 1.0.6)
-    diff-lcs (1.1.3)
-    domain_name (0.5.1)
-      unf (~> 0.0.3)
-    eventmachine (1.0.0)
-    eventmachine (1.0.0-java)
-    eventmachine (1.0.0-x86-mingw32)
-    ffi (1.0.11)
-    ffi (1.0.11-java)
-    gherkin (2.7.2)
-      json (>= 1.4.6)
-    gherkin (2.7.2-java)
-      json (>= 1.4.6)
-    gherkin (2.7.2-x86-mingw32)
-      json (>= 1.4.6)
-    git (1.2.5)
-    haml (4.0.1)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.12.1)
+      multi_json (>= 1.7.5, < 2.0)
+      multi_test (>= 0.0.2)
+    diff-lcs (1.2.4)
+    domain_name (0.5.14)
+      unf (>= 0.0.5, < 1.0.0)
+    faraday (0.8.8)
+      multipart-post (~> 1.2.0)
+    ffi (1.9.1)
+    ffi (1.9.1-java)
+    gherkin (2.12.2)
+      multi_json (~> 1.3)
+    gherkin (2.12.2-java)
+      multi_json (~> 1.3)
+    gherkin (2.12.2-x86-mingw32)
+      multi_json (~> 1.3)
+    git (1.2.6)
+    github_api (0.10.1)
+      addressable
+      faraday (~> 0.8.1)
+      hashie (>= 1.2)
+      multi_json (~> 1.4)
+      nokogiri (~> 1.5.2)
+      oauth2
+    haml (4.0.3)
       tilt
-    hashie (2.0.3)
-    httparty (0.9.0)
-      multi_json (~> 1.0)
-      multi_xml
-    jeweler (1.6.4)
+    hashie (2.0.5)
+    highline (1.6.20)
+    http-cookie (1.0.2)
+      domain_name (~> 0.5)
+    httparty (0.12.0)
+      json (~> 1.8)
+      multi_xml (>= 0.5.2)
+    httpauth (0.2.0)
+    jeweler (1.8.8)
+      builder
       bundler (~> 1.0)
       git (>= 1.2.5)
+      github_api (= 0.10.1)
+      highline (>= 1.6.15)
+      nokogiri (= 1.5.10)
       rake
-    jruby-openssl (0.7.4)
-      bouncy-castle-java
-    json (1.6.4)
-    json (1.6.4-java)
-    mechanize (2.1)
+      rdoc
+    jruby-openssl (0.9.4)
+      bouncy-castle-java (>= 1.5.0147)
+    json (1.8.1)
+    json (1.8.1-java)
+    jwt (0.1.8)
+      multi_json (>= 1.5)
+    mechanize (2.7.2)
       domain_name (~> 0.5, >= 0.5.1)
+      http-cookie (~> 1.0.0)
+      mime-types (~> 1.17, >= 1.17.2)
       net-http-digest_auth (~> 1.1, >= 1.1.1)
-      net-http-persistent (~> 2.3, >= 2.3.2)
+      net-http-persistent (~> 2.5, >= 2.5.2)
       nokogiri (~> 1.4)
       ntlm-http (~> 0.1, >= 0.1.1)
-      webrobots (~> 0.0, >= 0.0.9)
-    multi_json (1.3.6)
-    multi_xml (0.5.1)
-    net-http-digest_auth (1.2)
-    net-http-persistent (2.3.3)
-    nokogiri (1.5.0)
-    nokogiri (1.5.0-java)
-    nokogiri (1.5.0-x86-mingw32)
+      webrobots (>= 0.0.9, < 0.2)
+    mime-types (1.25)
+    multi_json (1.8.2)
+    multi_test (0.0.2)
+    multi_xml (0.5.5)
+    multipart-post (1.2.0)
+    net-http-digest_auth (1.4)
+    net-http-persistent (2.9)
+    nokogiri (1.5.10)
+    nokogiri (1.5.10-java)
+    nokogiri (1.5.10-x86-mingw32)
     ntlm-http (0.1.1)
+    oauth2 (0.9.2)
+      faraday (~> 0.8)
+      httpauth (~> 0.2)
+      jwt (~> 0.1.4)
+      multi_json (~> 1.0)
+      multi_xml (~> 0.5)
+      rack (~> 1.2)
     ptools (1.2.2)
     ptools (1.2.2-x86-mingw32)
       win32-file (>= 0.5.4)
-    rack (1.4.0)
-    rack-protection (1.2.0)
+    rack (1.5.2)
+    rack-protection (1.5.1)
       rack
-    rack-test (0.6.1)
+    rack-test (0.6.2)
       rack (>= 1.0)
-    rake (0.9.2.2)
-    rspec (2.11.0)
-      rspec-core (~> 2.11.0)
-      rspec-expectations (~> 2.11.0)
-      rspec-mocks (~> 2.11.0)
-    rspec-core (2.11.1)
-    rspec-expectations (2.11.3)
-      diff-lcs (~> 1.1.3)
-    rspec-mocks (2.11.3)
-    simplecov (0.6.4)
+    rake (10.1.0)
+    rdoc (4.0.1)
+      json (~> 1.4)
+    rspec (2.14.1)
+      rspec-core (~> 2.14.0)
+      rspec-expectations (~> 2.14.0)
+      rspec-mocks (~> 2.14.0)
+    rspec-core (2.14.6)
+    rspec-expectations (2.14.3)
+      diff-lcs (>= 1.1.3, < 2.0)
+    rspec-mocks (2.14.4)
+    simplecov (0.7.1)
       multi_json (~> 1.0)
-      simplecov-html (~> 0.5.3)
-    simplecov-html (0.5.3)
-    sinatra (1.3.2)
-      rack (~> 1.3, >= 1.3.6)
-      rack-protection (~> 1.2)
-      tilt (~> 1.3, >= 1.3.3)
-    sinatra-contrib (1.3.1)
+      simplecov-html (~> 0.7.1)
+    simplecov-html (0.7.1)
+    sinatra (1.4.4)
+      rack (~> 1.4)
+      rack-protection (~> 1.4)
+      tilt (~> 1.3, >= 1.3.4)
+    sinatra-contrib (1.4.1)
       backports (>= 2.0)
-      eventmachine
+      multi_json
       rack-protection
       rack-test
-      sinatra (~> 1.3.0)
+      sinatra (~> 1.4.0)
       tilt (~> 1.3)
-    term-ansicolor (1.0.7)
-    thor (0.15.4)
-    tilt (1.3.3)
-    unf (0.0.4)
+    thor (0.18.1)
+    tilt (1.4.1)
+    unf (0.1.3)
       unf_ext
-    unf_ext (0.0.4)
-    unf_ext (0.0.4-x86-mingw32)
+    unf (0.1.3-java)
+    unf_ext (0.0.6)
+    unf_ext (0.0.6-x86-mingw32)
     waitforit (0.0.1)
-    webrobots (0.0.12)
-      nokogiri (>= 1.4.4)
-    win32-api (1.4.8-x86-mingw32)
+    webrobots (0.1.1)
+    win32-api (1.5.0-x86-mingw32)
     win32-file (0.6.8)
       win32-api (>= 1.2.1)
       win32-file-stat (>= 1.3.2)

data/README.md

@@ -1,3 +1,4 @@
+[![Build Status](https://travis-ci.org/lashd/mirage.png)](https://travis-ci.org/lashd/mirage)
 Mirage
 ======
 Mirage aids testing of your applications by hosting mock responses so that your applications do not have to talk to real endpoints. It's accessible via HTTP and has a RESTful interface.    
@@ -10,7 +11,7 @@ I hope you find it useful,
 
 Leon
 
-P.s. Mirage runs on Linux,MacOSX and Windows; Rubies 1.8.7, 1.9 and JRuby.
+P.s. Mirage runs on Linux,MacOSX and Windows; Rubies 1.9.3+ and JRuby.
 
 Installation
 ------------

data/VERSION

@@ -1 +1 @@
-3.0.0.alpha.17
+3.0.0

data/features/.nav

@@ -17,3 +17,13 @@
 - logging.feature (Logs)
 - web_user_interface.feature
 - client (Ruby client):
+  - start.feature
+  - stop.feature
+  - running.feature
+  - put.feature
+  - configure.feature
+  - clear.feature
+  - preview_responses.feature
+  - model.feature
+  - requests.feature
+  - save_and_revert.feature

data/features/client/clear.feature

@@ -1,6 +1,8 @@
-Feature: The client can be used for clearing down Mirage.
+Feature: Clearing Templates
 
-  As with the restful interface, clearing a template also clears any associated request data
+  The client can be used to clear responses and tracked request data from Mirage.
+
+  Like when calling Mirage's own interface directly, clearing a template also clears any associated request data
 
   Background:
     Given the following require statements are needed:
@@ -35,7 +37,7 @@ Feature: The client can be used for clearing down Mirage.
     Then a 200 should be returned
 
 
-  Scenario: Clearning a request
+  Scenario: Clearing a request
     Given I run
     """
     Mirage::Client.new.requests(1).delete

data/features/client/configure.feature

@@ -1,10 +1,12 @@
-Feature: The client can be configured with default settings to keep your mocking 'DRY'
+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 gems are required to run the Mirage client test code:
     """
     require 'rubygems'
-    require 'rspec'
+    require 'rspec/expectations'
     require 'mirage/client'
     """
 

data/features/client/model.feature

@@ -0,0 +1,95 @@
+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 gems are required to run the Mirage client test code:
+    """
+    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,14 +1,16 @@
-Feature: the client can be used for peeking at responses hosted on Mirage.
+Feature: Inspecting Templates
+
+  The client can be used to retrieve a template stored on Mirage.
 
   Background:
     Given the following gems are required to run the Mirage client test code:
     """
     require 'rubygems'
-    require 'rspec'
+    require 'rspec/expectations'
     require 'mirage/client'
     """
 
-  Scenario: peeking a response
+  Scenario: retrieving a Template
     Given a template for 'greeting' has been set with a value of 'Hello'
 
     When I run
@@ -19,14 +21,13 @@ Feature: the client can be used for peeking at responses hosted on Mirage.
     When GET is sent to '/requests/1'
     Then a 404 should be returned
 
-  Scenario: getting a response that does not exist
+  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
-    puts e
-      e.is_a?(Mirage::ResponseNotFound).should == true
+      e.is_a?(Mirage::TemplateNotFound).should == true
     end
     """

data/features/client/prime.feature

@@ -0,0 +1,32 @@
+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 gems are required to run the Mirage client test code:
+    """
+    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