polygallery 0.1.1 → 0.1.2

data/test/dummy/spec/factories/events.rb

@@ -0,0 +1,7 @@
+include ActionDispatch::TestProcess
+
+FactoryGirl.define do
+  factory :event do
+    title { FFaker::BaconIpsum.words(3).join(' ').titleize }
+  end
+end

data/test/dummy/spec/factories/polygallery/photos.rb

@@ -0,0 +1,7 @@
+include ActionDispatch::TestProcess
+
+FactoryGirl.define do
+  factory :photo, :class => Polygallery::Photo do
+    caption { [nil, FFaker::BaconIpsum.paragraph].sample }
+  end
+end

data/test/dummy/spec/features/events_spec.rb

@@ -0,0 +1,60 @@
+require 'spec_helper'
+
+describe 'Events:', :js => true do
+  def add_photo_to_form(attrs=nil)
+    # attrs ||= build :photo
+    last_tr = all('.polygallery-photos-table tr').last
+    if last_tr.find('input[id$="_photo"]').value.present?
+      page.execute_script <<-SCRIPT
+        $('.btn.add_fields[data-association="photo"]').click();
+      SCRIPT
+      last_tr = all('.polygallery-photos-table tr').last
+    end
+    within last_tr do
+      find('input[id$="_photo"]').set Rails.root.join('spec', 'upload_files', 
+                                                      'logo_placeholder_medium.png')
+      find('input[id$="_caption"]').set('Test test test')
+      yield if block_given?
+    end
+  end
+
+  describe 'with SimpleForm' do
+    def complete_the_form(attrs=nil)
+      attrs ||= attributes_for :event
+      within 'form.simple_form.new_event' do
+        fill_in 'Title', :with => attrs[:title]
+        yield if block_given?
+        click_button 'Create Event'
+      end
+    end
+    def expect_success
+      expect(page).to have_content 'Your event has been saved!'
+    end
+    def expect_failure
+      expect(page).to have_content 'Your event could not be saved!'
+    end
+
+    it 'basically works' do
+      visit root_path
+      complete_the_form
+      expect_success
+      expect(Event.count).to eq 1
+    end
+
+    it 'works when an image is attached' do
+      visit root_path
+      complete_the_form { add_photo_to_form }
+      expect_success
+      expect(Event.count).to eq 1
+      e = Event.last
+      expect(e.custom_gallery_photos.count).to eq 1
+      photo = e.custom_gallery_photos.first
+      puts photo
+      expect(photo.photo.file?).to be true
+    end
+  end
+  
+  describe 'without SimpleForm' do
+    it 'basically works'
+  end
+end

data/test/dummy/spec/rails_helper.rb

@@ -0,0 +1,50 @@
+# This file is copied to spec/ when you run 'rails generate rspec:install'
+ENV['RAILS_ENV'] ||= 'test'
+require 'spec_helper'
+require File.expand_path('../../config/environment', __FILE__)
+require 'rspec/rails'
+# Add additional requires below this line. Rails is not loaded until this point!
+
+# Requires supporting ruby files with custom matchers and macros, etc, in
+# spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are
+# run as spec files by default. This means that files in spec/support that end
+# in _spec.rb will both be required and run as specs, causing the specs to be
+# run twice. It is recommended that you do not name files matching this glob to
+# end with _spec.rb. You can configure this pattern with the --pattern
+# option on the command line or in ~/.rspec, .rspec or `.rspec-local`.
+#
+# The following line is provided for convenience purposes. It has the downside
+# of increasing the boot-up time by auto-requiring all files in the support
+# directory. Alternatively, in the individual `*_spec.rb` files, manually
+# require only the support files necessary.
+#
+# Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }
+
+# Checks for pending migrations before tests are run.
+# If you are not using ActiveRecord, you can remove this line.
+ActiveRecord::Migration.maintain_test_schema!
+
+RSpec.configure do |config|
+  # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
+  config.fixture_path = "#{::Rails.root}/spec/fixtures"
+
+  # If you're not using ActiveRecord, or you'd prefer not to run each of your
+  # examples within a transaction, remove the following line or assign false
+  # instead of true.
+  config.use_transactional_fixtures = true
+
+  # RSpec Rails can automatically mix in different behaviours to your tests
+  # based on their file location, for example enabling you to call `get` and
+  # `post` in specs under `spec/controllers`.
+  #
+  # You can disable this behaviour by removing the line below, and instead
+  # explicitly tag your specs with their type, e.g.:
+  #
+  #     RSpec.describe UsersController, :type => :controller do
+  #       # ...
+  #     end
+  #
+  # The different available types are documented in the features, such as in
+  # https://relishapp.com/rspec/rspec-rails/docs
+  config.infer_spec_type_from_file_location!
+end

data/test/dummy/spec/spec_helper.rb

@@ -0,0 +1,138 @@
+# This file was generated by the `rails generate rspec:install` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# The `.rspec` file also contains a few flags that are not defaults but that
+# users commonly want.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+
+ENV["RAILS_ENV"] = 'test'
+require File.expand_path("../../../dummy/config/environment", __FILE__)
+require 'rspec/rails'
+require 'selenium-webdriver'
+require 'capybara/rails'
+require 'capybara/dsl'
+require 'factory_girl_rails'
+require 'database_cleaner'
+require 'ffaker'
+require 'sass'
+
+Capybara.app_host = 'http://localhost:3003'
+Capybara.server_port = 3003
+Capybara.default_wait_time = 15
+Capybara.register_driver :chrome do |app|
+  Capybara::Selenium::Driver.new(app, :browser => :chrome)
+end
+Capybara.javascript_driver = :chrome # :poltergeist 
+
+# Requires supporting ruby files with custom matchers and macros, etc,
+# in spec/support/ and its subdirectories.
+Dir[Rails.root.join("spec/support/**/*.rb")].each { |f| require f }
+
+# Checks for pending migrations before tests are run.
+# If you are not using ActiveRecord, you can remove this line.
+ActiveRecord::Migration.maintain_test_schema!
+
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  config.order = "random"
+
+  config.include FactoryGirl::Syntax::Methods
+
+  config.infer_spec_type_from_file_location!
+
+  config.use_transactional_fixtures = false
+
+  config.before :each do
+    ActionMailer::Base.deliveries = []
+    if Capybara.current_driver == :rack_test
+      DatabaseCleaner.strategy = :transaction
+    else
+      DatabaseCleaner.strategy = :truncation
+    end
+    DatabaseCleaner.start
+  end
+
+  config.after do
+    DatabaseCleaner.clean
+  end
+
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # These two settings work together to allow you to limit a spec run
+  # to individual examples or groups you care about by tagging them with
+  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
+  # get run.
+  config.filter_run :focus
+  config.run_all_when_everything_filtered = true
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
+  #   - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
+  config.disable_monkey_patching!
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = 'doc'
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

data/test/dummy/tmp/pids/server.pid

@@ -0,0 +1 @@
+55735