alberich 0.2.0

data/spec/models/alberich/privilege_spec.rb

@@ -0,0 +1,39 @@
+require 'spec_helper'
+
+module Alberich
+  describe Privilege do
+    it "should require unique action for target and role" do
+      role1 = FactoryGirl.create(:role)
+      role2 = FactoryGirl.create(:role)
+      priv1 = FactoryGirl.create(:privilege, :action => "create",
+                                 :target_type => "Alberich::BasePermissionObject",
+                                 :role_id => role1.id)
+      priv2 = FactoryGirl.create(:privilege, :action => "create",
+                                 :target_type => "Alberich::BasePermissionObject",
+                                 :role_id => role2.id)
+      priv2.role = priv1.role
+      priv2.should_not be_valid
+    end
+    it "should enforce validity of action" do
+      role1 = FactoryGirl.create(:role)
+      u = FactoryGirl.create(:privilege, :role_id => role1.id)
+      u.valid?.should be_true
+      u.action = "I'm Invalid"
+      u.valid?.should be_false
+      u.errors[:action].should_not be_nil
+      u.errors[:action][0].should =~ /^is not included in the list.*/
+    end
+
+    it "should enforce validity of target_type" do
+      role1 = FactoryGirl.create(:role)
+      u = FactoryGirl.create(:privilege, :role_id => role1.id)
+      u.valid?.should be_true
+      u.target_type = "I'm Invalid"
+      u.valid?.should be_false
+      u.errors[:target_type].should_not be_nil
+      u.errors[:target_type][0].should =~ /^is not included in the list.*/
+    end
+
+
+  end
+end

data/spec/models/alberich/role_spec.rb

@@ -0,0 +1,33 @@
+require 'spec_helper'
+
+module Alberich
+  describe Role do
+    it "should not be valid if name is too long" do
+      u = FactoryGirl.create(:role)
+      u.name = ('a' * 256)
+      u.valid?.should be_false
+      u.errors[:name].should_not be_nil
+      u.errors[:name][0].should =~ /^is too long.*/
+    end
+
+    it "should enforce validity of scope" do
+      u = FactoryGirl.create(:role)
+      u.valid?.should be_true
+      u.scope = "I'm Invalid"
+      u.valid?.should be_false
+      u.errors[:scope].should_not be_nil
+      u.errors[:scope][0].should =~ /^is not included in the list.*/
+    end
+
+    it "should require unique name" do
+      role1 = FactoryGirl.create(:role)
+      role2 = FactoryGirl.create(:role)
+      role1.should be_valid
+      role2.should be_valid
+
+      role2.name = role1.name
+      role2.should_not be_valid
+    end
+
+  end
+end

data/spec/models/alberich/session_entity_spec.rb

@@ -0,0 +1,24 @@
+require 'spec_helper'
+
+module Alberich
+  describe SessionEntity do
+    it "should require unique entity for user and session" do
+      user = FactoryGirl.create(:user)
+      group1 = FactoryGirl.create(:user_group)
+      group2 = FactoryGirl.create(:user_group)
+      session = FactoryGirl.create(:permission_session, :user_id=>user.id)
+      entity1 = SessionEntity.new(:permission_session_id => session.id,
+                                  :user_id => user.id,
+                                  :entity_id => Entity.for_target(group1).id)
+      entity1.should be_valid
+      entity1.save!
+      entity2 = SessionEntity.new(:permission_session_id => session.id,
+                                  :user_id => user.id,
+                                  :entity_id => Entity.for_target(group2).id)
+      entity2.should be_valid
+      entity2.entity = entity1.entity
+      entity2.should_not be_valid
+    end
+
+  end
+end

data/spec/spec_helper.rb

@@ -0,0 +1,81 @@
+# Setup Rails Envinronment
+ENV["RAILS_ENV"] = "test"
+require File.expand_path("../../test/dummy/config/environment.rb",  __FILE__)
+require 'rspec/rails'
+require 'factory_girl'
+
+ENGINE_RAILS_ROOT=File.join(File.dirname(__FILE__), '../')
+
+# Requires supporting ruby files with custom matchers and macros, etc,
+# in spec/support/ and its subdirectories.
+
+Dir[File.join(ENGINE_RAILS_ROOT, "spec/support/**/*.rb")].each {|f| require f }
+Dir.glob(File.join(File.dirname(__FILE__) + "/factories/", "**", "*.rb")).each do |file|
+  require file
+end
+
+RSpec.configure do |config|
+  config.color_enabled = true
+  config.formatter     = 'documentation'
+  config.use_transactional_fixtures = true
+
+  config.include Warden::Test::Helpers, :type => :request
+  config.after(:each, :type => :request) do
+    Warden.test_reset!
+  end
+  config.backtrace_clean_patterns = [
+    /\/lib\d*\/ruby\//,
+    /bin\//,
+    #/gems/,
+    #/spec\/spec_helper\.rb/,
+    /lib\/rspec\/(core|expectations|matchers|mocks)/
+  ]
+end
+
+# Override to_xml to use underscore rather than dash
+ActiveRecord::Base.class_eval do
+  def to_xml(options={})
+    options[:dasherize] ||= false
+    super({ :root => self.class.name.split("::").last.underscore }.merge(options))
+  end
+end
+
+module RequestContentTypeHelper
+  def accept_all
+    @request.env["HTTP_ACCEPT"] = "*/*"
+  end
+
+  def accept_json
+    @request.env["HTTP_ACCEPT"] = "application/json"
+  end
+
+  def accept_xml
+    @request.env["HTTP_ACCEPT"] = "application/xml"
+  end
+
+  def send_and_accept_xml
+    @request.env["HTTP_ACCEPT"] = "application/xml"
+    @request.env["CONTENT_TYPE"] = "application/xml"
+  end
+
+  def send_and_accept_json
+    @request.env["HTTP_ACCEPT"] = "application/json"
+    @request.env["CONTENT_TYPE"] = "application/json"
+  end
+end
+
+include RequestContentTypeHelper
+def mock_warden(user)
+  request.env['warden'] = mock(Warden, :authenticate => user,
+                                       :authenticate! => user,
+                                       :user => user,
+                                       :raw_session => nil)
+  @session_id = 'ee73441902cb9445483e498cb05dc398'
+  request.session_options[:id] = @session_id
+  if user
+    @permission_session = Alberich::PermissionSession.create!(:user => user,
+                                                    :session_id => @session_id)
+    request.session[:permission_session_id] = @permission_session.id
+    @permission_session.update_session_entities(user)
+  end
+end

data/spec/support/routes.rb

@@ -0,0 +1,41 @@
+# Sets up use_route across controller tests, from:
+# http://bit.ly/PU4Wm4 (stackoverflow)
+
+module ControllerSetup
+  def get(action, parameters = nil, session = nil, flash = nil)
+    process_action(action, parameters, session, flash, "GET")
+  end
+
+  # Executes a request simulating POST HTTP method and set/volley the
+  # response
+  def post(action, parameters = nil, session = nil, flash = nil)
+    process_action(action, parameters, session, flash, "POST")
+  end
+
+  # Executes a request simulating PUT HTTP method and set/volley the
+  # response
+  def put(action, parameters = nil, session = nil, flash = nil)
+    process_action(action, parameters, session, flash, "PUT")
+  end
+
+  # Executes a request simulating DELETE HTTP method and set/volley
+  # the response
+  def delete(action, parameters = nil, session = nil, flash = nil)
+    process_action(action, parameters, session, flash, "DELETE")
+  end
+
+  private
+
+  def process_action(action, parameters = nil, session = nil, flash = nil, method = "GET")
+    parameters ||= {}
+    process(action, parameters.merge!(:use_route => :alberich), session, flash, method)
+  end
+end
+
+RSpec.configure do |c|
+   # This will include the routing helpers in the specs so that we can
+   # use base_image_path and so on to get to the routes.
+   c.include Alberich::Engine.routes.url_helpers
+   # Always use the correct route for controller tests
+   c.include ControllerSetup, :type => :controller
+end

data/test/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== 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.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.org/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
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+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. 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.