paper_trail_manager 0.1.6 → 0.2.0

data/rails_test/Rakefile

@@ -0,0 +1,90 @@
+if ENV['BUNDLE_GEMFILE']
+  STDERR.puts <<-HERE
+========================================================================
+
+ERROR: Cannot test 'paper_trail_manager' because Bundler is loaded!
+
+Do not use 'bundle exec rake' or otherwise load Bundler into the Rake
+environment. This test suite runs across multiple versions of Rails and
+needs to be able to setup individual environments for each of these, and
+it can't do this if Bundler is already loaded.
+
+========================================================================
+  HERE
+  raise
+end
+
+def run(cmd)
+  puts "* running: #{cmd}"
+  system cmd
+  raise "ERROR running command" unless $? == 0
+end
+
+def setup_rails_app dir
+  dir =~ /rails-([^-]+)/
+  version = $1
+  run "./generate_test_directory #{version}"
+  bundler_cache = File.expand_path("bundler_cache")
+  Dir.chdir dir do
+    File.open("Gemfile", "w") do |gemfile|
+      gemfile.write <<-GEM
+        source :gemcutter
+        gem "rails", "=#{version}"
+        gem "sqlite3-ruby", :require => "sqlite3"
+        gem "rake"
+        gem "will_paginate", "~> 3.0.pre2"
+        gem "paper_trail_manager", :path => "#{File.expand_path(File.join(File.dirname(__FILE__), '..', '..', '..'))}"
+        gem 'factory_girl_rails', '~> 1.7.0'
+        gem 'rspec-rails', '~> 2.11.0'
+      GEM
+    end
+    run "bundle install --path=#{bundler_cache}"
+  end
+end
+
+def test_rails_app dir
+  @results ||= {}
+  Dir.chdir(dir) do
+    ENV['RAILS_ENV'] = "test"
+    FileUtils.mkdir_p "log"
+    begin
+      run "touch db/test.sqlite3" # db:create doesn't exist before rails 2.0
+      run "bundle exec rake db:migrate --trace"
+      # run "bundle exec rspec --backtrace spec"
+      run "bundle exec rake"
+    rescue Object
+      @results[dir] = "FAIL"
+    else
+      @results[dir] = "SUCCESS"
+    end
+  end
+end
+
+def print_results
+  puts "----- RESULTS -----"
+  @results.keys.sort.each do |key|
+    puts "* #{key}: #{@results[key]}"
+  end
+end
+
+Dir["#{File.dirname(__FILE__)}/rails-*"].sort.each do |fqdir|
+  dir = File.basename fqdir
+  desc "test #{dir}"
+  task "test:#{dir}" do
+    Dir.chdir(File.dirname(__FILE__)) do
+      setup_rails_app dir
+      test_rails_app dir
+    end
+  end
+end
+
+namespace :test do
+  desc "run tests across various versions of Rails"
+  task :rails do
+    Dir["#{File.dirname(__FILE__)}/rails-*"].sort.reverse.each do |fqdir|
+      dir = File.basename fqdir
+      Rake::Task["test:#{dir}"].invoke
+    end
+    print_results
+  end
+end

data/{spec/dummy → rails_test/common}/app/models/entity.rb

@@ -1,6 +1,8 @@
 class Entity < ActiveRecord::Base
   has_paper_trail
 
+  attr_accessible :name, :status
+
   validates_presence_of :name
   validates_presence_of :status
 end

data/{spec/dummy → rails_test/common}/app/models/platform.rb

@@ -1,6 +1,8 @@
 class Platform < ActiveRecord::Base
   has_paper_trail
 
+  attr_accessible :name, :status
+
   validates_presence_of :name
   validates_presence_of :status
 end

data/{spec/dummy → rails_test/common}/spec/integration/navigation_spec.rb

@@ -2,6 +2,6 @@ require 'spec_helper'
 
 describe "Navigation" do
   it "should be a valid app" do
-    ::Rails.application.should be_a(Dummy::Application)
+    ::Rails.application.should be_a_kind_of(Rails::Application)
   end
 end

data/{spec/dummy → rails_test/common}/spec/integration/paper_trail_manager_spec.rb

@@ -102,9 +102,10 @@ describe PaperTrailManager do
           end
         end
 
-        context "when not authorized" do
-          it "should display an error if user is not allowed to list changes"
-        end
+        # TODO
+        # context "when not authorized" do
+        #   it "should display an error if user is not allowed to list changes"
+        # end
       end
 
       context "when getting changes for a specific type" do
@@ -120,9 +121,10 @@ describe PaperTrailManager do
           end
         end
 
-        context "that doesn't exist" do
-          it "should display ana error that the type doesn't exist"
-        end
+        # TODO
+        # context "that doesn't exist" do
+        #   it "should display ana error that the type doesn't exist"
+        # end
       end
 
       context "when getting changes for a specific record" do
@@ -142,9 +144,10 @@ describe PaperTrailManager do
           end
         end
 
-        context "that doesn't exist" do
-          it "should display an error that the record doesn't exist"
-        end
+        # TODO
+        # context "that doesn't exist" do
+        #   it "should display an error that the record doesn't exist"
+        # end
       end
     end
 
@@ -169,14 +172,16 @@ describe PaperTrailManager do
           end
         end
 
-        context "when not authorized" do
-          it "should display an error if user is not allowed to show the change"
-        end
+        # TODO
+        # context "when not authorized" do
+        #   it "should display an error if user is not allowed to show the change"
+        # end
       end
 
-      context "that doesn't exist" do
-        it "should display an error that the change doesn't exist"
-      end
+      # TODO
+      # context "that doesn't exist" do
+      #   it "should display an error that the change doesn't exist"
+      # end
     end
   end
 
@@ -213,13 +218,15 @@ describe PaperTrailManager do
         end
       end
 
-      context "when not authorized" do
-          it "should display an error if user is not allowed to revert that change"
-      end
+      # TODO
+      # context "when not authorized" do
+      #   it "should display an error if user is not allowed to revert that change"
+      # end
     end
 
-    context "that don't exist" do
-      it "should display an error that the change doesn't exist"
-    end
+    # TODO
+    # context "that don't exist" do
+    #   it "should display an error that the change doesn't exist"
+    # end
   end
 end

data/rails_test/common/spec/spec_helper.rb

@@ -0,0 +1,32 @@
+require 'rubygems'
+
+# Configure Rails Envinronment
+ENV["RAILS_ENV"] = "test"
+
+require File.expand_path("../../config/environment.rb",  __FILE__)
+require "rails/test_help"
+require "rspec/rails"
+
+ActionMailer::Base.delivery_method = :test
+ActionMailer::Base.perform_deliveries = true
+ActionMailer::Base.default_url_options[:host] = "test.com"
+
+Rails.backtrace_cleaner.remove_silencers!
+
+# Run any available migration
+ActiveRecord::Migrator.migrate File.expand_path("../../db/migrate/", __FILE__)
+
+# Load support files
+Dir["#{File.dirname(__FILE__)}/support/**/*.rb"].each { |f| require f }
+
+RSpec.configure do |config|
+  # Remove this line if you don't want RSpec's should and should_not
+  # methods or matchers
+  require 'rspec/expectations'
+  config.include RSpec::Matchers
+
+  # == Mock Framework
+  config.mock_with :rspec
+
+  config.use_transactional_fixtures = true
+end

data/rails_test/generate_test_directory

@@ -0,0 +1,59 @@
+#! /usr/bin/env ruby
+
+unless ARGV[0]
+  puts "USAGE: #{File.basename($0)} <rails-version>"
+  puts
+  puts " e.g., '#{File.basename($0)} 3.2.8'"
+  puts
+  exit 1
+end
+
+version = ARGV[0]
+
+require "rubygems"
+
+Dir.chdir(File.dirname(__FILE__))
+
+def run(cmd)
+  puts "* running '#{cmd}'"
+  system cmd
+  raise "command failed" unless $? == 0
+end
+
+def rails version, dir
+  begin
+    gem "rails", "=#{version}"
+  rescue Gem::LoadError => e
+    puts "ERROR: could not find rails version #{version}"
+    puts "Try running:"
+    puts "  gem install rails --version=#{version}"
+    exit 1
+  end
+  puts "* successfully detected rails version #{version}"
+  if version >= "3"
+    run "yes | rails _#{version}_ new #{dir} > /dev/null"
+  else
+    run "yes | rails _#{version}_ #{dir} > /dev/null"
+  end
+end
+
+dir = "rails-#{version}"
+rails version, dir unless File.exists?(dir)
+
+# Copy common files
+run "rsync -a common/ #{dir}"
+
+# Rewrite routes to add paper_trail_manager
+body = <<-HERE
+  root :to => 'application#index'
+
+  resources :changes, :controller => 'paper_trail_manager/changes'
+  resources :entities
+  resources :platforms
+HERE
+file = "#{dir}/config/routes.rb"
+data = File.read(file)
+File.open(file, "w") do |handle|
+  data.sub!(/(\A[^\n]+\n)(.+)(\nend\s*\Z)/m, "\\1#{body}\\3")
+  handle.write(data)
+end

data/rails_test/rails-3.0.17/.gitignore

@@ -0,0 +1,4 @@
+.bundle
+db/*.sqlite3
+log/*.log
+tmp/

data/rails_test/rails-3.0.17/README

@@ -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, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== 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/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two 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 <tt>sudo gem install ruby-debug</tt>. 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", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, 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 can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. 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.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.com/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+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>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |   |-- images
+  |   |-- javascripts
+  |   `-- stylesheets
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      `-- plugins
+
+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. Models descend from
+  ActiveRecord::Base by default.
+
+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 by default.
+
+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 generators 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 rails generate
+  command, 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.