spina-admin-conferences-blog 0.1.0

data/spec/models/spina/admin/conferences/blog/post_spec.rb

@@ -0,0 +1,39 @@
+# frozen_string_literal: true
+
+require 'rails_helper'
+
+module Spina::Admin::Conferences::Blog
+  RSpec.describe Post, type: :model do
+    let(:post) { build(:spina_blog_post) }
+
+    subject { post }
+
+    it { is_expected.to be_valid }
+    it { expect { post.save }.to change(Spina::Admin::Conferences::Blog::Post, :count).by(1) }
+
+    context 'with invalid attributes' do
+      let(:post) { build(:invalid_spina_blog_post) }
+
+      it { is_expected.to_not be_valid }
+      it { expect { post.save }.to_not change(Spina::Admin::Conferences::Blog::Post, :count) }
+    end
+
+    describe '.featured' do
+      let!(:post) { create(:spina_blog_post, featured: true) }
+      let!(:unfeatured) { create(:spina_blog_post) }
+
+      it 'returns 1 result' do
+        expect(Spina::Admin::Conferences::Blog::Post.featured).to match_array [post]
+      end
+    end
+
+    describe '.unfeatured' do
+      let!(:post) { create(:spina_blog_post, featured: true) }
+      let!(:unfeatured) { create(:spina_blog_post) }
+
+      it 'returns 1 result' do
+        expect(Spina::Admin::Conferences::Blog::Post.unfeatured).to match_array [unfeatured]
+      end
+    end
+  end
+end

data/spec/rails_helper.rb

@@ -0,0 +1,68 @@
+# frozen_string_literal: true
+
+require 'simplecov'
+SimpleCov.start 'rails'
+
+# This file is copied to spec/ when you run 'rails generate rspec:install'
+require 'spec_helper'
+ENV['RAILS_ENV'] ||= 'test'
+require File.expand_path('dummy/config/environment.rb', __dir__)
+ActiveRecord::Migrator.migrations_paths = [File.expand_path('dummy/db/migrate', __dir__)]
+# Prevent database truncation if the environment is production
+abort('The Rails environment is running in production mode!') if Rails.env.production?
+require 'rspec/rails'
+# Add additional requires below this line. Rails is not loaded until this point!
+require 'factory_bot_rails'
+require 'capybara/rails'
+require 'capybara/rspec'
+require 'webdrivers'
+
+# 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 }
+Dir[File.expand_path('../spec/support/**/*.rb', __dir__)].each { |f| require f }
+
+# Checks for pending migration and applies them 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!
+
+  # Filter lines from Rails gems in backtraces.
+  config.filter_rails_from_backtrace!
+  # arbitrary gems may also be filtered via:
+  # config.filter_gems_from_backtrace("gem name")
+end

data/spec/spec_helper.rb

@@ -0,0 +1,97 @@
+# frozen_string_literal: true
+
+# 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.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+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
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+  # The settings below are suggested to provide a good initial experience
+  # with RSpec, but feel free to customize to your heart's content.
+
+  # This allows 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. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = 'spec/examples.txt'
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  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

data/spec/support/capybara.rb

@@ -0,0 +1,25 @@
+# frozen_string_literal: true
+
+Capybara.server = :puma, { Silent: true }
+
+args = %w[disable-dev-shm-usage no-sandbox disable-gpu window-size=1280,1024]
+args << "lang=#{I18n.locale}"
+args << 'headless' unless ENV['DEBUG']
+capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(
+  chromeOptions: { args: args }
+)
+
+Capybara.register_driver :chrome do |app|
+  Capybara::Selenium::Driver.new(
+    app, browser: :chrome, desired_capabilities: capabilities
+  )
+end
+
+Capybara.register_driver :selenium_remote do |app|
+  Capybara::Selenium::Driver.new(
+    app,
+    browser: :remote,
+    desired_capabilities: capabilities,
+    url: 'http://selenium:4444/wd/hub'
+  )
+end

data/spec/support/controller_helpers.rb

@@ -0,0 +1,25 @@
+# frozen_string_literal: true
+
+module ControllerHelpers
+  def sign_in
+    @account = Spina::Account.create name: 'My Website', preferences: { theme: 'default' }
+    @user = Spina::User.create name: 'admin', email: 'admin@example.com', password: 'password', admin: true
+    request.session[:user_id] = @user.id
+  end
+end
+
+module FeatureHelpers
+  def sign_in
+    @account = Spina::Account.create name: 'My Website', preferences: { theme: 'default' }
+    @user = Spina::User.create name: 'admin', email: 'admin@example.com', password: 'password', admin: true
+    visit '/admin/login'
+    fill_in :email, with: @user.email
+    fill_in :password, with: 'password'
+    click_button 'Login'
+  end
+end
+
+RSpec.configure do |config|
+  config.include ControllerHelpers, type: :controller
+  config.include FeatureHelpers, type: :system
+end

data/spec/support/controller_routes.rb

@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+module ControllerRoutes
+  extend ActiveSupport::Concern
+
+  included do
+    routes { Spina::Engine.routes }
+  end
+end
+
+RSpec.configure do |c|
+  c.include ControllerRoutes, type: :controller
+end

data/spec/support/factory_bot.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+RSpec.configure do |config|
+  config.include FactoryBot::Syntax::Methods
+end

data/spec/support/rails_controller_testing.rb

@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+require 'rails-controller-testing'
+
+RSpec.configure do |config|
+  %i[controller view request].each do |type|
+    config.include ::Rails::Controller::Testing::TestProcess, type: type
+    config.include ::Rails::Controller::Testing::TemplateAssertions, type: type
+    config.include ::Rails::Controller::Testing::Integration, type: type
+  end
+
+  config.include ::Rails::Controller::Testing::TemplateAssertions, type: :helper
+end

data/spec/support/system_tests.rb

@@ -0,0 +1,11 @@
+# frozen_string_literal: true
+
+RSpec.configure do |c|
+  c.before(:each, type: :system) do
+    driven_by :rack_test
+  end
+
+  c.before(:each, type: :system, js: true) do
+    driven_by :selenium
+  end
+end

data/spec/system/spina/admin/conferences/blog/posts_spec.rb

@@ -0,0 +1,34 @@
+# frozen_string_literal: true
+
+require 'rails_helper'
+
+RSpec.feature 'Admin Posts', type: :system do
+  before { sign_in }
+
+  describe 'listing posts' do
+    let!(:posts) { create_list(:spina_blog_post, 3, published_at: Date.today + 1) }
+
+    it 'shows all the posts' do
+      visit '/admin/conferences/blog/posts'
+      expect(page).to have_css 'tbody tr', count: 3
+    end
+  end
+
+  describe 'creating a post' do
+    it 'creates a post', js: true do
+      visit '/admin/conferences/blog/posts'
+      click_on 'New Post'
+      fill_in 'Post title', with: 'Title of Blog post'
+      find(
+        :css, 'trix-editor[input*="content_input"]'
+      ).set('Foobar')
+      click_on 'Save post'
+      within '#header' do
+        click_on 'Posts'
+      end
+      within 'tbody' do
+        expect(page).to have_content 'Title of Blog post'
+      end
+    end
+  end
+end