mirage-on-thin 3.0.8

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 62b859169722e9d419435c65f7406d62c8d696f1
+  data.tar.gz: 0fd4b89ec3c0414af7bee9bc247c3221e17d4b13
+SHA512:
+  metadata.gz: 3aa820fa3ff4484d74777840b4d9445cfb3d4bab2121c5ce9b1a7a01b31569172c9eb17ce9a72060b619badcecaaaf431edbaa6535e896069135fe0aa1305b97
+  data.tar.gz: 5dd72fc9d2b33df6096e452e8c19ea52e095e82b155ba18fe929dc1524839b1d5de97a233f3af03683067ae03effb8243d3ccc6d5d374d811c377a89619521ff

data/.ruby-gemset

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

data/.ruby-version

@@ -0,0 +1 @@
+2.0.0-p353

data/.simplecov

@@ -0,0 +1,6 @@
+SimpleCov.start do
+  command_name "spec:#{ENV['coverage']}"
+  add_filter "/spec/"
+  add_group "Server", "server"
+  add_group "Client", "lib"
+end

data/.travis.yml

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

data/Gemfile

@@ -0,0 +1,29 @@
+source 'https://rubygems.org'
+
+gem 'sinatra'
+gem 'thin'
+gem 'childprocess'
+gem "waitforit"
+gem "thor"
+gem "ptools"
+gem "httparty"
+gem "haml"
+gem 'hashie'
+
+group :test do
+  gem 'cucumber'
+  gem 'rspec', require: 'rspec/core/rake_task'
+  gem 'rack-test'
+  gem 'simplecov', require: false
+end
+
+group :development do
+  gem 'rake'
+  gem "jeweler"
+  gem 'sinatra-contrib'
+
+  platform :jruby do
+    gem "jruby-openssl"
+  end
+end
+  

data/Gemfile.lock

@@ -0,0 +1,151 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    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.3)
+      gherkin (~> 2.12.1)
+      multi_json (>= 1.7.5, < 2.0)
+      multi_test (>= 0.0.2)
+    daemons (1.1.9)
+    diff-lcs (1.2.4)
+    eventmachine (1.0.3)
+    faraday (0.8.8)
+      multipart-post (~> 1.2.0)
+    ffi (1.9.0)
+    ffi (1.9.0-java)
+    ffi (1.9.0-x86-mingw32)
+    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.5)
+    highline (1.6.20)
+    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
+      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)
+    multi_json (1.8.2)
+    multi_test (0.0.2)
+    multi_xml (0.5.5)
+    multipart-post (1.2.0)
+    nokogiri (1.5.10)
+    nokogiri (1.5.10-java)
+    nokogiri (1.5.10-x86-mingw32)
+    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.5.2)
+    rack-protection (1.5.1)
+      rack
+    rack-test (0.6.2)
+      rack (>= 1.0)
+    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.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)
+      multi_json
+      rack-protection
+      rack-test
+      sinatra (~> 1.4.0)
+      tilt (~> 1.3)
+    thin (1.6.2)
+      daemons (>= 1.0.9)
+      eventmachine (>= 1.0.0)
+      rack (>= 1.0.0)
+    thor (0.18.1)
+    tilt (1.4.1)
+    waitforit (0.0.1)
+    win32-api (1.5.0-x86-mingw32)
+    win32-file (0.6.8)
+      win32-api (>= 1.2.1)
+      win32-file-stat (>= 1.3.2)
+      windows-pr (>= 1.0.8)
+    win32-file-stat (1.3.6)
+      windows-pr (>= 1.0.0)
+    windows-api (0.4.2)
+      win32-api (>= 1.4.5)
+    windows-pr (1.2.2)
+      win32-api (>= 1.4.5)
+      windows-api (>= 0.3.0)
+
+PLATFORMS
+  java
+  ruby
+  x86-mingw32
+
+DEPENDENCIES
+  childprocess
+  cucumber
+  haml
+  hashie
+  httparty
+  jeweler
+  jruby-openssl
+  ptools
+  rack-test
+  rake
+  rspec
+  simplecov
+  sinatra
+  sinatra-contrib
+  thin
+  thor
+  waitforit

data/HISTORY

@@ -0,0 +1,22 @@
+V3.0.8 - bug fix for issue 13: https://github.com/lashd/mirage/issues/13 - match Content-Length header
+V3.0.7 - bug fix for issue 13: https://github.com/lashd/mirage/issues/13 - match Content-Type header
+V3.0.6 - bug fix
+V3.0.5 - fixed bug in builder methods
+V3.0.1 - updating gem post install message to point people towards the readme due checkout the differences between version 2 and 3 of Mirage
+V3.0.0 - Major update see README.md
+V2.4.2 - update eventmachine, make sure Mirage.start always returns a client
+V2.4.1 - adding rdoc for configure method
+V2.4.0 - Adding ability to set defaults
+V2.3.0 - Enhanced commandline/programmatic api
+V2.2.3 - fix bug where mirage is already running a client calls exit.
+V2.2.1/2 - Code tidy up
+V2.2.0 - Api for starting and stopping Mirage locally
+V2.1.2 - rename status_code to status
+V2.1.1 - Set response code and tidy ups
+V2.0.16 - minor typo fix for window command window title in windows
+V2.0.15 - fix uploading files from client and fix starting mirage on windows
+V2.0.12/13/14 - updating gem versions
+V2.0.8/9/10/11 - tidy up code, still a lot to do :)
+V2.0.7 - fix missing dependency on waitforit gem
+V2.0.1/2/3 - tidying up code
+V2.0.0 - Converted to restful interface

data/README.md

@@ -0,0 +1,156 @@
+[![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.    
+
+Any ideas/improvements or feedback you have are greatly appreciated.  
+  
+Information on how to use Mirage can be found [here](https://github.com/lashd/mirage/wiki).  
+  
+I hope you find it useful,  
+
+Leon
+
+P.s. Mirage runs on Linux,MacOSX and Windows; Rubies 1.9.3+ and JRuby.
+
+Installation
+------------
+    gem install mirage 
+    
+What's New?
+-----------
+### 3.0.0
+------------------------------
+3.0.0 is now out the following is a description of what's new.
+
+A full description of the functionality is also available in the projects [feature files](https://www.relishapp.com/lashd/mirage/docs) hosted on Relish. A lot of effort has gone in to trying to make these tests readable so if something is missing or unclear drop me a line.
+
+
+#### What's new in the Server:
+##### 1: Mirage uses JSON as its communucations medium
+Mirage is now configured using JSON. JSON is also used as the output format for Mirage's other operations.
+##### 2: Wildcards are now supported in the URI.
+You can now specify wild cards in the URI matcher. This means that a url such as '/*/world' would match '/hello/world' :)
+##### 3: Full Request Data now tracked
+You can now retrieve all data associated with a request that triggers a response. Previously only the the request body/query string was tracked.
+Now the full request, including HTTP headers are returned when querying '/requests/template_id'
+
+##### 4. Parameters and body content matchers are now specified seperately
+Now you can specify as many parameter and body matchers as you want. These can be both litteral strings or Regex's
+  
+Previously, it was only possible to specify a single matcher and this would be applied against both the querystring and the request body.
+##### 5. HTTP Header matchers
+You can now also specify matchers against HTTP headers.
+##### 6. More advanced template resolution.
+Templates are now scored to find the most appropriate template when finding a match for a particular request. Previously the first potential match was returned even
+if there was a more appropriate template.
+
+Litteral matchers are worth more in the scoring process than regex based ones for example.
+##### 7. The url has changed
+Mirage is now accessible via: http://localhost:7001. I.e. 'mirage' has been removed from all resources 
+
+e.g. responses are now under http://localhost:7001/responses
+##### 8. Default responses directory renamed to mirage
+Default templates used to be stored in a directory named 'responses'. The term 'response' was the incorrect word to describe what is now called a 'template'. Rather than rename this directory to templates, which is a directory name that may already be in use in your project, the default name for this directory has been changed to 'mirage'.  
+  
+The old directory name can still be used if you use the client or command line interface to overide where the responses are loaded from
+
+#### What's new in the Client:
+##### 1. Template Models
+Perhaps the biggest addition to the client. Simply mixin Mirage::Template::Model in to a class, give it a method called body and there you have it... a class that can be used to put objects straight on to Mirage.
+ 
+* All the methods you find on a standard response can then be used at the class level to set defaults. 
+ 
+* Add builder methods to your class using the builder_methods class method.
+ 
+**Example Usage:** (See rdoc for full details)  
+
+    class UserProfile
+      extend Mirage::Template::Model
+      
+      endpoint '/users'
+      http_method :get
+      status 200
+      content_type 'application/json'
+      
+      builder_methods :firstname, :lastname, :age
+      
+      def body
+        {firstname: firstname, lastname: lastname, age: age}.to_json
+      end
+    end
+    
+    
+    Mirage::Client.new.put UserProfile.new.firstname('Joe').lastname('blogs')
+    
+##### Client interface
+The client interface has been overhauled to make it more usable. It supports a couple of different ways of specifying a template
+to let to specify templates in the style that best suites your code. The block in the examples is executed in the scope of the template
+object itself so any method in it can be called. The template is also passed in to the block if you prefer to to call the methods
+on a variable.
+
+**Example Usage:** (See rdoc for full details)  
+
+    mirage = Mirage::Client.new
+    mirage.put('/users') do
+      status 201
+      http_method :put
+      body 'response'
+      
+      required_body_content << 'Abracadabra'
+      required_headers['Header'] = 'value'
+      
+      delay 1.5
+    end
+    
+    # Template Model classes can be customised in exactly the same way
+    
+    mirage.put UserProfile.new do
+      status 404
+      required_parameters[:name] = /joe.*/
+    end
+#### What you don't get
+A better UI :) it's on its way though!
+
+### 2.4.0
+---------
+#### What do I get?
+##### 1: Configure your client with defaults for each of your responses
+Remove the repetition of setting things like the content-type each to time you put a response on to Mirage
+
+**Example Usage:** (See rdoc for full details)  
+
+    client = Mirage::Client.new do |defaults|
+      defaults.content_type = "text/xml"
+      defaults.delay = 0.5
+    end  
+    
+    client.put("greeting", "hello") -> template put on to Mirage with a delay of 0.5 seconds and content-type text/xml configured
+#### What do I have to do to upgrade?
+Nothing, this is a new feature. Let me know if you have any problems :)
+    
+    
+
+
+### 2.3.0
+---------
+#### What do I get?
+##### 1: Run more than one instance of Mirage per machine.
+##### 2: Programmatic interface for starting and stopping Mirage
+The client API now includes the ability to start and stop Mirage locally. No more calling out to the command line.  
+
+**Example Usage:** (See rdoc for full details)  
+
+    mirage_client = Mirage.start :port => 9001 #with out args start mirage on 7001 by default
+    Mirage.stop # stops the current running instance as long as only one is running  
+    
+##### 3: Updated command line interface
+Now powered by the mighty Thor, the stop subcommand has been enhanced.  
+**Usage:**  
+
+    mirage stop -> As it always did, stops the current instances of Mirage as long as there is only one running instance.  
+    mirage stop -p port -> stops Mirage on a given port.    
+    mirage stop -p port1, port2... -> stop multiple instances of Mirage.  
+    mirage stop -p all -> stop all instances of mirage.  
+#### What do I have to do to upgrade?
+You shouldn't have to do anything to move from the last version of Mirage to this one. Let me know if something stops working!

data/Rakefile

@@ -0,0 +1,10 @@
+require 'bundler/setup'
+
+Bundler.setup(:default, :development)
+Bundler.require(:test, :development)
+
+Dir["#{File.dirname(__FILE__)}/tasks/**/*.rake"].each do |tasks|
+  import tasks
+end
+
+task :default => [:specs, :install, :features, :clean]

data/VERSION

@@ -0,0 +1 @@
+3.0.8

data/bin/mirage

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+require 'rubygems'
+
+
+$LOAD_PATH.unshift("#{File.dirname(__FILE__)}/../lib")
+require 'mirage/client'
+
+begin
+  Mirage::Runner.start
+rescue Mirage::ClientError => e
+  puts e.message
+  exit 1
+end
+

data/features/.nav

@@ -0,0 +1,29 @@
+- commandline_interface (Commandline interface):
+  - help.feature
+  - start.feature
+  - stop.featre
+- templates (Templates):
+  - put.feature
+  - required_content.feature
+  - put_with_substitutions.feature
+  - get.feature
+  - delete.feature
+- requests:
+- get.feature
+- delete.feature
+- requests:
+- save_and_revert.feature (Snapshot)
+- prime.feature
+- 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