realweb 0.1.0 → 0.1.4

data/README.rdoc

@@ -1,24 +1,47 @@
 = RealWeb
 
-Boot a rack app in a thread or process to use as a real test endpoint.
+Boot a rack app to use as a real endpoint for tests.
 
-=== Usage
+== Why?
 
-    before(:each) do
-      @server = RealWeb.start_server("path/to/config.ru")
-    end
+We found this very useful for gems that hit an API. Rather than mocking out all
+the URIs with FakeWeb, you can just write a sample rack app that looks like the
+API you're expecting. It's not uncommon to have 5+ different small rack apps
+that reflect different behaviors of your remote server. We created things like
+broken.ru that always responds with 500s, forbidden.ru that is always 403, and
+healthy.ru that always returns happy path responses.
 
-    after(:each) do
-      @server.stop
-    end
+Another useful way to use this is with paired client/server libraries. We use
+RealWeb to boot up the real rack server and hit it with the client from within
+the specs.
+
+== Usage
+
+    # fixtures/config.ru
+    run lambda { |env| [200, { 'Content-Type' => 'application/json' }, '[{thing: 1}, {thing: 2}]'] }
+
+    # thing_api_spec.rb
+    describe MyLibrary do
+      before(:each) do
+        @server = RealWeb.start_server("fixtures/config.ru")
+      end
 
-    it "runs some action that would normally hit the api" do
-      MyLibrary.get_list_of_things(@server.base_uri)
+      after(:each) do
+        @server.stop
+      end
+
+      it "runs an action that would normally hit the api" do
+        MyLibrary.get_list_of_things_from_api(@server.base_uri).should_not be_empty
+      end
     end
 
 
-RealWeb.start_server boots the given config.ru in a thread. When you call stop on the server object, the server is killed.
+RealWeb.start_server boots the given config.ru in a thread. When you call stop
+on the server object, the server is killed.
 
-You can specifically use a Process.fork server with start_server_in_fork.
+The example uses an extremely simplistic rack app. We usually use Sinatra apps
+for RealWeb backends.
 
-RealWeb uses WEBrick for its pure ruby server. No extra dependencies or C extensions.
+== Forking Server
+
+You can specifically use a Process.fork server with start_server_in_fork.

data/lib/realweb/server.rb

@@ -99,7 +99,6 @@ module RealWeb
           open(base_uri)
           return
         rescue Errno::ECONNREFUSED
-          puts "Connection refused; retrying..."
           sleep 0.5
         end
       end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: realweb
 version: !ruby/object:Gem::Version 
-  hash: 27
+  hash: 19
   prerelease: false
   segments: 
   - 0
   - 1
-  - 0
-  version: 0.1.0
+  - 4
+  version: 0.1.4
 platform: ruby
 authors: 
 - Ben Burkert
@@ -17,11 +17,10 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-05-28 00:00:00 -07:00
+date: 2010-06-01 00:00:00 -07:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
-  prerelease: false
   version_requirements: &id001 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
@@ -34,8 +33,9 @@ dependencies:
         - 0
         version: 1.1.0
   requirement: *id001
-  type: :runtime
   name: rack
+  type: :runtime
+  prerelease: false
 description: Easily runs a rack app for tests that hit web APIs
 email: cloud-engineering@engineyard.com
 executables: []