catarse_full 0.0.1

data/spec/controllers/users/projects_controller_spec.rb

@@ -0,0 +1,19 @@
+require 'spec_helper'
+
+describe Users::ProjectsController do
+  let(:project) { create(:project) }
+  let(:user) { create(:user) }
+
+  subject{ response }
+
+  before do
+    controller.stub(:current_user).and_return(user)
+  end
+
+  describe "GET index" do
+    before do
+      get :index, { locale: :pt, user_id: project.user_id }
+    end
+    its(:status){ should eq 200 }
+  end
+end

data/spec/controllers/users_controller_spec.rb

@@ -0,0 +1,92 @@
+#encoding:utf-8
+require 'spec_helper'
+
+describe UsersController do
+  render_views
+  subject{ response }
+  before do
+    controller.stub(:current_user).and_return(current_user)
+  end
+
+  let(:successful_project){ FactoryGirl.create(:project, state: 'successful') }
+  let(:failed_project){ FactoryGirl.create(:project, state: 'failed') }
+  let(:backer){ FactoryGirl.create(:backer, state: 'confirmed', user: user, project: failed_project) }
+  let(:user){ FactoryGirl.create(:user, password: 'current_password', password_confirmation: 'current_password', authorizations: [FactoryGirl.create(:authorization, uid: 666, oauth_provider: FactoryGirl.create(:oauth_provider, name: 'facebook'))]) }
+  let(:current_user){ user }
+
+  describe "PUT update" do
+    before do
+      put :update, id: user.id, locale: 'pt', user: { twitter: 'test' }
+    end
+    it("should update the user") do
+      user.reload
+      user.twitter.should ==  'test'
+    end
+    it{ should redirect_to user_path(user, anchor: 'settings') }
+  end
+
+  describe "GET set_email" do
+    before do
+      get :set_email, locale: 'pt'
+    end
+    it{ should render_template('set_email') }
+  end
+
+  describe "PUT update_password" do
+    let(:current_password){ 'current_password' }
+    let(:password){ 'newpassword123' }
+    let(:password_confirmation){ 'newpassword123' }
+    before do
+      put :update_password, id: user.id, locale: 'pt', user: { current_password: current_password, password: password, password_confirmation: password_confirmation }
+    end
+
+    context "with wrong current password" do
+      let(:current_password){ 'wrong_password' }
+      it{ flash[:error].should_not be_empty }
+      it{ should redirect_to user_path(user, anchor: 'settings') }
+    end
+
+    context "with right current password and right confirmation" do
+      it{ flash[:notice].should_not be_empty }
+      it{ flash[:error].should be_nil }
+      it{ should redirect_to user_path(user, anchor: 'settings') }
+    end
+  end
+
+  describe "PUT update_email" do
+    let(:email){ 'new_email@bar.com' }
+    let(:return_to){ nil }
+    before do
+      session[:return_to] = return_to
+      put :update_email, id: user.id, locale: 'pt', user: {email: email}
+    end
+
+    context "when email is not valid" do
+      let(:email){ 'new_email_bar.com' }
+      it{ should render_template('set_email') }
+    end
+
+    context "when email is valid and we have a session[:return_to]" do
+      let(:return_to){ '/foo' }
+      it{ should redirect_to return_to }
+      it{ session[:return_to].should be_nil }
+    end
+
+    context "when email is valid" do
+      it("should update the user") do
+        user.reload
+        user.email.should ==  'new_email@bar.com'
+      end
+      it{ should redirect_to user_path(user, anchor: 'settings') }
+    end
+  end
+
+  describe "GET show" do
+    before do
+      FactoryGirl.create(:notification_type, name: 'updates')
+      get :show, id: user.id, locale: 'pt'
+    end
+
+    it{ assigns(:fb_admins).should include(user.facebook_id.to_i) }
+  end
+end

data/spec/decorators/project_decorator_spec.rb

@@ -0,0 +1,146 @@
+require 'spec_helper'
+
+describe ProjectDecorator do
+  let(:project){ create(:project, about: 'Foo Bar http://www.foo.bar <javascript>xss()</javascript>"Click here":http://click.here') }
+
+  describe "#display_expires_at" do
+    subject{ project.display_expires_at }
+
+    context "when online_date is nil" do
+      let(:project){ create(:project, online_date: nil) }
+      it{ should == '' }
+    end
+
+    context "when we have an online_date" do
+      let(:project){ create(:project, online_date: Time.now) }
+      before do
+        I18n.should_receive(:l).with(project.expires_at.to_date)
+      end
+      it("should call I18n with date"){ subject }
+    end
+  end
+
+  describe "#display_image" do
+    subject{ project.display_image }
+
+    context "when we have a video_url without thumbnail" do
+      let(:project){ create(:project, uploaded_image: nil, video_thumbnail: nil) }
+      it{ should == project.video.thumbnail_large }
+    end
+
+    context "when we have a video_thumbnail" do
+      let(:project){ create(:project, video_thumbnail: File.open("#{Catarse::Engine.root}/spec/fixtures/image.png")) }
+      it{ should == project.video_thumbnail.project_thumb.url }
+    end
+
+    context "when we have an uploaded_image" do
+      let(:project){ create(:project, uploaded_image: File.open("#{Catarse::Engine.root}/spec/fixtures/image.png"), video_thumbnail: nil) }
+      it{ should == project.uploaded_image.project_thumb.url }
+    end
+  end
+
+  describe "#about_html" do
+    subject{ project.about_html }
+    it{ should == '<p>Foo Bar <a href="http://www.foo.bar" target="_blank">http://www.foo.bar</a> &lt;javascript&gt;xss()&lt;/javascript&gt;<a target="_blank" href="http://click.here">Click here</a></p>' }
+  end
+
+  describe "#display_progress" do
+    subject{ project.display_progress }
+    context "when progress is 0" do
+      before{ project.stub(:progress).and_return(0) }
+      it{ should == 0 }
+    end
+    context "when progress is between 0 and 8" do
+      before{ project.stub(:progress).and_return(7) }
+      it{ should == 8 }
+    end
+    context "when progress is between 8 and 100" do
+      before{ project.stub(:progress).and_return(70) }
+      it{ should == 70 }
+    end
+    context "when progress is above 100" do
+      before{ project.stub(:progress).and_return(101) }
+      it{ should == 100 }
+    end
+  end
+
+  describe "#display_status" do
+    subject{ project.display_status }
+    context "when online and reached goal" do
+      before do
+        project.stub(:state).and_return('online')
+        project.stub(:reached_goal?).and_return(true)
+      end
+      it{ should == 'reached_goal' }
+    end
+    context "when online and have not reached goal yet" do
+      before do
+        project.stub(:state).and_return('online')
+        project.stub(:reached_goal?).and_return(false)
+      end
+      it{ should == 'not_reached_goal' }
+    end
+    context "when failed" do
+      before do
+        project.stub(:state).and_return('failed')
+      end
+      it{ should == 'failed' }
+    end
+    context "when successful" do
+      before do
+        project.stub(:state).and_return('successful')
+      end
+      it{ should == 'successful' }
+    end
+    context "when waiting funds" do
+      before do
+        project.stub(:state).and_return('waiting_funds')
+      end
+      it{ should == 'waiting_funds' }
+    end
+  end
+
+  describe '#display_video_embed_url' do
+    subject{ project.display_video_embed_url }
+
+    context 'source has a Vimeo video' do
+      let(:project) { create(:project, video_url: 'http://vimeo.com/17298435') }
+
+      it { should == 'http://player.vimeo.com/video/17298435?title=0&byline=0&portrait=0&autoplay=0' }
+    end
+
+    # In catarse.me we accept only vimeo videos, but feel free to uncomment this in your fork
+    # and adjust the project model accordingly :D
+    #context 'source has an Youtube video' do
+      #let(:project) { create(:project, video_url: "http://www.youtube.com/watch?v=Brw7bzU_t4c") }
+
+      #it { should == 'http://www.youtube.com/embed/Brw7bzU_t4c?title=0&byline=0&portrait=0&autoplay=0' }
+    #end
+
+    context 'source does not have a video' do
+      let(:project) { create(:project, video_url: "") }
+
+      it { should be_nil }
+    end
+  end
+
+
+  describe "#successful_flag" do
+    let(:project) { create(:project) }
+
+    context "When the project is successful" do
+      it "should return a successful image flag when the project is successful" do
+        project.stub(:successful?).and_return(true)
+
+        expect(project.successful_flag).to eq('<div class="successful_flag"><img alt="Successful" src="/assets/channels/successful.png" /></div>')
+      end
+    end
+
+    context "When the project was not successful" do
+      it "should not return an image, but nil" do
+        expect(project.successful_flag).to eq(nil)
+      end
+    end
+  end
+end
+

data/spec/decorators/user_decorator_spec.rb

@@ -0,0 +1,87 @@
+require 'spec_helper'
+
+describe UserDecorator do
+  before(:all) do
+    I18n.locale = :pt
+  end
+
+  describe "#display_name" do
+    subject{ user.display_name }
+
+    context "when we only have a full name" do
+      let(:user){ create(:user, name: nil, full_name: "Full Name") }
+      it{ should == 'Full Name' }
+    end
+
+    context "when we have only a name" do
+      let(:user){ create(:user, name: nil, name: 'name') }
+      it{ should == 'name' }
+    end
+
+    context "when we have a name and a full name" do
+      let(:user){ create(:user, name: 'name', full_name: 'full name') }
+      it{ should == 'name' }
+    end
+
+    context "when we have no name" do
+      let(:user){ create(:user, name: nil, nickname: nil) }
+      it{ should == I18n.t('user.no_name') }
+    end
+  end
+
+  describe "#display_image_html" do
+    let(:user){ build(:user, image_url: 'image.jpg', uploaded_image: nil )}
+    let(:options){ {width: 300, height: 300} }
+    subject{ user.display_image_html(options) }
+    it{ should == "<div class=\"avatar_wrapper\" style=\"width: #{options[:width]}px; height: #{options[:height]}px\"><img alt=\"User\" src=\"/assets/#{user.display_image}\" style=\"width: #{options[:width]}px; height: auto\" /></div>" }
+  end
+
+  describe "#display_image" do
+    subject{ user.display_image }
+
+    context "when we have an uploaded image" do
+      let(:user){ build(:user, uploaded_image: 'image.png' )}
+      before do
+        image = stub(url: 'image.png')
+        image.stub(:thumb_avatar).and_return(image)
+        user.stub(:uploaded_image).and_return(image)
+      end
+      it{ should == 'image.png' }
+    end
+
+    context "when we have an image url" do
+      let(:user){ build(:user, image_url: 'image.png') }
+      it{ should == 'image.png' }
+    end
+
+    context "when we have an email" do
+      let(:user){ create(:user, image_url: nil, email: 'diogob@gmail.com') }
+      it{ should == "https://gravatar.com/avatar/5e2a237dafbc45f79428fdda9c5024b1.jpg?default=#{::Configuration[:base_url]}/assets/user.png" }
+    end
+  end
+
+  describe "#short_name" do
+    subject { user = create(:user, name: 'My Name Is Lorem Ipsum Dolor Sit Amet') }
+    its(:short_name) { should == 'My Name Is Lorem ...' }
+  end
+
+  describe "#medium_name" do
+    subject { user = create(:user, name: 'My Name Is Lorem Ipsum Dolor Sit Amet And This Is a Bit Name I Think') }
+    its(:medium_name) { should == 'My Name Is Lorem Ipsum Dolor Sit Amet A...' }
+  end
+
+  describe "#display_credits" do
+    subject { create(:user) }
+    its(:display_credits) { should == 'R$ 0'}
+  end
+
+  describe "#display_total_of_backs" do
+    subject { user = create(:user) }
+    context "with confirmed backs" do
+      before do
+        create(:backer, state: 'confirmed', user: subject, value: 500.0)
+      end
+      its(:display_total_of_backs) { should == 'R$ 500'}
+    end
+  end
+end

data/spec/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.