RubyGems - remi-rackbox - Versions diffs - 1.0.1 → 1.1.0 - Mend

remi-rackbox 1.0.1 → 1.1.0

Files changed (80) hide show

data/README.markdown +6 -0
data/Rakefile +57 -0
data/VERSION.yml +2 -2
data/examples/rack/config.ru +53 -0
data/examples/rack/run-specs +2 -0
data/examples/rack/spec +1 -0
data/examples/rails/README +256 -0
data/examples/rails/Rakefile +10 -0
data/examples/rails/app/controllers/application.rb +15 -0
data/examples/rails/app/controllers/welcome_controller.rb +32 -0
data/examples/rails/app/helpers/application_helper.rb +3 -0
data/examples/rails/app/helpers/welcome_helper.rb +2 -0
data/examples/rails/app/views/layouts/application.html.erb +7 -0
data/examples/rails/app/views/welcome/some_html.html.erb +20 -0
data/examples/rails/config/boot.rb +109 -0
data/examples/rails/config/database.yml +22 -0
data/examples/rails/config/environment.rb +75 -0
data/examples/rails/config/environments/development.rb +17 -0
data/examples/rails/config/environments/production.rb +24 -0
data/examples/rails/config/environments/test.rb +22 -0
data/examples/rails/config/initializers/inflections.rb +10 -0
data/examples/rails/config/initializers/mime_types.rb +5 -0
data/examples/rails/config/initializers/new_rails_defaults.rb +17 -0
data/examples/rails/config/locales/en.yml +5 -0
data/examples/rails/config/routes.rb +12 -0
data/examples/rails/db/development.sqlite3 +0 -0
data/examples/rails/db/schema.rb +14 -0
data/examples/rails/db/test.sqlite3 +0 -0
data/examples/rails/doc/README_FOR_APP +5 -0
data/examples/rails/lib/tasks/rspec.rake +158 -0
data/examples/rails/public/404.html +30 -0
data/examples/rails/public/422.html +30 -0
data/examples/rails/public/500.html +33 -0
data/examples/rails/public/dispatch.cgi +10 -0
data/examples/rails/public/dispatch.fcgi +24 -0
data/examples/rails/public/dispatch.rb +10 -0
data/examples/rails/public/favicon.ico +0 -0
data/examples/rails/public/images/rails.png +0 -0
data/examples/rails/public/javascripts/application.js +2 -0
data/examples/rails/public/javascripts/controls.js +963 -0
data/examples/rails/public/javascripts/dragdrop.js +973 -0
data/examples/rails/public/javascripts/effects.js +1128 -0
data/examples/rails/public/javascripts/prototype.js +4320 -0
data/examples/rails/public/robots.txt +5 -0
data/examples/rails/run-specs +2 -0
data/examples/rails/script/about +4 -0
data/examples/rails/script/autospec +5 -0
data/examples/rails/script/console +3 -0
data/examples/rails/script/dbconsole +3 -0
data/examples/rails/script/destroy +3 -0
data/examples/rails/script/generate +3 -0
data/examples/rails/script/performance/benchmarker +3 -0
data/examples/rails/script/performance/profiler +3 -0
data/examples/rails/script/performance/request +3 -0
data/examples/rails/script/plugin +3 -0
data/examples/rails/script/process/inspector +3 -0
data/examples/rails/script/process/reaper +3 -0
data/examples/rails/script/process/spawner +3 -0
data/examples/rails/script/runner +3 -0
data/examples/rails/script/server +3 -0
data/examples/rails/script/spec +5 -0
data/examples/rails/script/spec_server +125 -0
data/examples/rails/spec +1 -0
data/examples/rails/test/functional/welcome_controller_test.rb +8 -0
data/examples/rails/test/performance/browsing_test.rb +9 -0
data/examples/rails/test/test_helper.rb +38 -0
data/examples/sinatra/config.ru +11 -0
data/examples/sinatra/run-specs +2 -0
data/examples/sinatra/sinatra_app.rb +58 -0
data/examples/sinatra/spec +1 -0
data/lib/rackbox/rack/extensions_for_rspec.rb +2 -0
data/lib/rackbox/rackbox.rb +32 -0
data/lib/rackbox/spec/configuration.rb +11 -0
data/lib/rackbox/spec/helpers.rb +1 -1
data/rails_generators/blackbox_spec/USAGE +5 -0
data/rails_generators/blackbox_spec/blackbox_spec_generator.rb +56 -0
data/rails_generators/blackbox_spec/templates/spec.erb +9 -0
data/spec/rackbox_spec.rb +35 -0
data/spec/spec_helper.rb +1 -0
metadata +106 -2

data/README.markdown CHANGED

@@ -61,6 +61,12 @@ on how things work in [Merb][] so I can duplicate any functionality I'm missing.
 `request` gives you a [`Rack::Response`](http://rack.rubyforge.org/doc/classes/Rack/Response.html) which has
 `body`, `headers`, `status` methods ([and more](http://rack.rubyforge.org/doc/classes/Rack/Response.html))
+TODO
+----
+Before I make a screencast and post it to my blog, I wanna finish these ...
+ - add a rails generator so you can install the gem and then ./script/generate blackbox\_spec
 [rackbox]:  http://github.com/remi/rackbox

data/Rakefile ADDED

@@ -0,0 +1,57 @@
+require 'rake'
+require 'rubygems'
+require 'rake/rdoctask'
+require 'spec/rake/spectask'
+begin
+  require 'jeweler'
+  Jeweler::Tasks.new do |s|
+    s.name        = "rackbox"
+    s.summary     = "Merb-like BlackBox testing for Rack apps, including Rails"
+    s.email       = "remi@remitaylor.com"
+    s.homepage    = "http://github.com/remi/rackbox"
+    s.description = "Merb-like BlackBox testing for Rack apps, including Rails"
+    s.authors     = %w( remi )
+    s.files       = FileList["[A-Z]*", "{lib,spec,examples,rails_generators}/**/*"]
+    # s.executables = "neato"
+    # s.add_dependency 'person-project'
+  end
+rescue LoadError
+  puts "Jeweler not available. Install it with: sudo gem install technicalpickles-jeweler -s http://gems.github.com"
+end
+Spec::Rake::SpecTask.new do |t|
+  t.spec_files = FileList['spec/**/*_spec.rb']
+end
+desc "Run all examples with RCov"
+Spec::Rake::SpecTask.new('rcov') do |t|
+  t.spec_files = FileList['spec/**/*_spec.rb']
+  t.rcov = true
+end
+Rake::RDocTask.new do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'rackbox'
+  rdoc.options << '--line-numbers' << '--inline-source'
+  rdoc.rdoc_files.include('README*')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+desc 'Confirm that gemspec is $SAFE'
+task :safe do
+  require 'yaml'
+  require 'rubygems/specification'
+  data = File.read('rackbox.gemspec')
+  spec = nil
+  if data !~ %r{!ruby/object:Gem::Specification}
+    Thread.new { spec = eval("$SAFE = 3\n#{data}") }.join
+  else
+    spec = YAML.load(data)
+  end
+  spec.validate
+  puts spec
+  puts "OK"
+end
+task :default => :spec

data/VERSION.yml CHANGED

@@ -1,4 +1,4 @@
 ---
-:patch: 1
 :major: 1
-:minor: 0
+:minor: 1
+:patch: 0

data/examples/rack/config.ru ADDED

@@ -0,0 +1,53 @@
+use Rack::Session::Cookie
+run lambda { |env|
+  request  = Rack::Request.new env
+  response = Rack::Response.new
+  params   = request.params
+  session  = env['rack.session']
+  response.body = case request.path_info
+  when '/'
+    "You said #{ params['say'] || 'nothing' }"
+  when '/print-method'
+    request.request_method.downcase
+  when '/print-session'
+    session['session_variable'] = params['session_variable'] if params['session_variable']
+    session['session_variable']
+  when '/redirect'
+    response.headers['Location'] = params['to']
+    response.status = 302 # manually set!
+    ''
+  when '/relative'
+    response.headers['Location'] = '/i_am_relative'
+    response.status = 302 # manually set!
+    ''
+  when '/some_text'
+    "hello there, how goes it?"
+  when '/some_html'
+    %q{
+      <html>
+        <head></head>
+        <body>
+          <p id="this-one"></p>
+          <p id="bacon-one"></p>
+          <div id="chunky-one">
+            <b>chunky one</b>
+            <div></div>
+          </div>
+        </body>
+      </html>
+    }
+  else
+    "DON'T KNOW HOWTO RESPOND TO PATH: #{ request.path_info }"
+  end.to_s
+  response.finish
+}

data/examples/rack/run-specs ADDED

	@@ -0,0 +1,2 @@
1	+ #! /bin/bash
2	+ spec --color spec//_spec.rb

data/examples/rack/spec ADDED

	@@ -0,0 +1 @@
1	+ ../.shared_specs

data/examples/rails/README ADDED

@@ -0,0 +1,256 @@
+== Welcome to Rails
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+This pattern splits the view (also called the presentation) into "dumb" templates
+that are primarily responsible for inserting pre-built data in between HTML tags.
+The model contains the "smart" domain objects (such as Account, Product, Person,
+Post) that holds all the business logic and knows how to persist themselves to
+a database. The controller handles the incoming requests (such as Save New Account,
+Update Product, Show Post) by manipulating the model and directing data to the view.
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails.  You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+== Getting Started
+1. At the command prompt, start a new Rails application using the <tt>rails</tt> command
+   and your application name. Ex: rails myapp
+2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
+3. Go to http://localhost:3000/ and get "Welcome aboard: You're riding the Rails!"
+4. Follow the guidelines to start developing your application
+== Web Servers
+By default, Rails will try to use Mongrel and lighttpd if they are installed, otherwise
+Rails will use WEBrick, the webserver that ships with Ruby. When you run script/server,
+Rails will check if Mongrel exists, then lighttpd and finally fall back to WEBrick. This ensures
+that you can always get up and running quickly.
+Mongrel is a Ruby-based webserver with a C component (which requires compilation) that is
+suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
+getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
+More info at: http://mongrel.rubyforge.org
+If Mongrel is not installed, Rails will look for lighttpd. It's considerably faster than
+Mongrel and WEBrick and also suited for production use, but requires additional
+installation and currently only works well on OS X/Unix (Windows users are encouraged
+to start with Mongrel). We recommend version 1.4.11 and higher. You can download it from
+http://www.lighttpd.net.
+And finally, if neither Mongrel or lighttpd are installed, Rails will use the built-in Ruby
+web server, WEBrick. WEBrick is a small Ruby web server suitable for development, but not
+for production.
+But of course its also possible to run Rails on any platform that supports FCGI.
+Apache, LiteSpeed, IIS are just a few. For more information on FCGI,
+please visit: http://wiki.rubyonrails.com/rails/pages/FastCGI
+== Apache .htaccess example
+# General Apache options
+AddHandler fastcgi-script .fcgi
+AddHandler cgi-script .cgi
+Options +FollowSymLinks +ExecCGI
+# If you don't want Rails to look in certain directories,
+# use the following rewrite rules so that Apache won't rewrite certain requests
+#
+# Example:
+#   RewriteCond %{REQUEST_URI} ^/notrails.*
+#   RewriteRule .* - [L]
+# Redirect all requests not available on the filesystem to Rails
+# By default the cgi dispatcher is used which is very slow
+#
+# For better performance replace the dispatcher with the fastcgi one
+#
+# Example:
+#   RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
+RewriteEngine On
+# If your Rails application is accessed via an Alias directive,
+# then you MUST also set the RewriteBase in this htaccess file.
+#
+# Example:
+#   Alias /myrailsapp /path/to/myrailsapp/public
+#   RewriteBase /myrailsapp
+RewriteRule ^$ index.html [QSA]
+RewriteRule ^([^.]+)$ $1.html [QSA]
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
+# In case Rails experiences terminal errors
+# Instead of displaying this message you can supply a file here which will be rendered instead
+#
+# Example:
+#   ErrorDocument 500 /500.html
+ErrorDocument 500 "<h2>Application error</h2>Rails application failed to start properly"
+== Debugging Rails
+Sometimes your application goes wrong.  Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+First area to check is the application log files.  Have "tail -f" commands running
+on the server.log and development.log. Rails will automatically display debugging
+and runtime information to these files. Debugging info will also be shown in the
+browser on requests from 127.0.0.1.
+You can also log your own messages directly into the log file from your code using
+the Ruby logger class from inside your controllers. Example:
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+The result will be a message in your log file along the lines of:
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+Also, Ruby documentation can be found at http://www.ruby-lang.org/ including:
+* The Learning Ruby (Pickaxe) Book: http://www.ruby-doc.org/docs/ProgrammingRuby/
+* Learn to Program: http://pine.fm/LearnToProgram/  (a beginners guide)
+These two online (and free) books will bring you up to speed on the Ruby language
+and also on programming in general.
+== Debugger
+Debugger support is available through the debugger command when you start your Mongrel or
+Webrick server with --debugger. This means that you can break out of execution at any point
+in the code, investigate and change the model, AND then resume execution!
+You need to install ruby-debug to run the server in debugging mode. With gems, use 'gem install ruby-debug'
+Example:
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      debugger
+    end
+  end
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
+       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+...and even better is that you can examine how your runtime objects actually work:
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+Finally, when you're ready to resume execution, you enter "cont"
+== Console
+You can interact with the domain model by starting the console through <tt>script/console</tt>.
+Here you'll have all parts of the application configured, just like it is when the
+application is running. You can inspect domain models, change values, and save to the
+database. Starting the script without arguments will launch it in the development environment.
+Passing an argument will specify a different environment, like <tt>script/console production</tt>.
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+== dbconsole
+You can go to the command line of your database directly through <tt>script/dbconsole</tt>.
+You would be connected to the database with the credentials defined in database.yml.
+Starting the script without arguments will connect you to the development database. Passing an
+argument will connect you to a different database, like <tt>script/dbconsole production</tt>.
+Currently works for mysql, postgresql and sqlite.
+== Description of Contents
+app
+  Holds all the code that's specific to this particular application.
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from ApplicationController
+  which itself descends from ActionController::Base.
+app/models
+  Holds models that should be named like post.rb.
+  Most models will descend from ActiveRecord::Base.
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use eRuby
+  syntax.
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the common
+  header/footer method of wrapping views. In your views, define a layout using the
+  <tt>layout :default</tt> and create a file named default.html.erb. Inside default.html.erb,
+  call <% yield %> to render the view using this layout.
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are generated
+  for you automatically when using script/generate for controllers. Helpers can be used to
+  wrap functionality for your views into methods.
+config
+  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
+db
+  Contains the database schema in schema.rb.  db/migrate contains all
+  the sequence of Migrations for your schema.
+doc
+  This directory is where your application documentation will be stored when generated
+  using <tt>rake doc:app</tt>
+lib
+  Application specific libraries. Basically, any kind of custom code that doesn't
+  belong under controllers, models, or helpers. This directory is in the load path.
+public
+  The directory available for the web server. Contains subdirectories for images, stylesheets,
+  and javascripts. Also contains the dispatchers and the default HTML files. This should be
+  set as the DOCUMENT_ROOT of your web server.
+script
+  Helper scripts for automation and generation.
+test
+  Unit and functional tests along with fixtures. When using the script/generate scripts, template
+  test files will be generated for you and placed in this directory.
+vendor
+  External libraries that the application depends on. Also includes the plugins subdirectory.
+  If the app has frozen rails, those gems also go here, under vendor/rails/.
+  This directory is in the load path.

data/examples/rails/Rakefile ADDED

@@ -0,0 +1,10 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+require(File.join(File.dirname(__FILE__), 'config', 'boot'))
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+require 'tasks/rails'

data/examples/rails/app/controllers/application.rb ADDED

@@ -0,0 +1,15 @@
+# Filters added to this controller apply to all controllers in the application.
+# Likewise, all the methods added will be available for all controllers.
+class ApplicationController < ActionController::Base
+  helper :all # include all helpers, all the time
+  # See ActionController::RequestForgeryProtection for details
+  # Uncomment the :secret if you're not using the cookie session store
+  protect_from_forgery # :secret => '1a02857159f22076b23409627bb4457b'
+  # See ActionController::Base for details
+  # Uncomment this to filter the contents of submitted sensitive data parameters
+  # from your application log (in this case, all fields with names like "password").
+  # filter_parameter_logging :password
+end

data/examples/rails/app/controllers/welcome_controller.rb ADDED

@@ -0,0 +1,32 @@
+class WelcomeController < ApplicationController
+  def index
+    render :text => "You said #{ params[:say] || 'nothing' }"
+  end
+  def print_method
+    render :text => request.method
+  end
+  def print_session
+    session[:session_variable] = params[:session_variable] if params[:session_variable]
+    render :text => session[:session_variable].to_s
+  end
+  def redirect
+    redirect_to params[:to]
+  end
+  def some_text
+    render :text => "well hello there \n how goes it? \n does it go well?"
+  end
+  def some_html
+    # render template
+  end
+  def relative
+    redirect_to '/i_am_relative'
+  end
+end