From f17d788bf6b39cb1aa1d4355b6f777bbfa8f3dad Mon Sep 17 00:00:00 2001 From: Ari Timonen Date: Sun, 22 Mar 2020 15:36:16 +0200 Subject: [PATCH] Add helpers back after mistake --- spec/rails_helper.rb | 65 +++++++++++++++++ spec/spec_helper.rb | 161 +++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 226 insertions(+) create mode 100644 spec/rails_helper.rb create mode 100755 spec/spec_helper.rb diff --git a/spec/rails_helper.rb b/spec/rails_helper.rb new file mode 100644 index 0000000..f8ea0a7 --- /dev/null +++ b/spec/rails_helper.rb @@ -0,0 +1,65 @@ +# Load spec_helper +require 'spec_helper' + +# This file is copied to spec/ when you run 'rails generate rspec:install' +ENV['RAILS_ENV'] ||= 'test' +require File.expand_path('../../config/environment', __FILE__) + +# Prevent database truncation if the environment is production +abort("The Rails environment is running in production mode!") if Rails.env.production? + +# Load rails +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| + #config.include Controllers::JsonHelpers, type: :controller + config.include Features::FormHelpers, type: :feature + config.include Features::ServerHelpers, type: :feature + config.include Features::SessionHelpers, type: :feature + + config.include Controllers::SessionHelpers, :type => :controller + + # 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 diff --git a/spec/spec_helper.rb b/spec/spec_helper.rb new file mode 100755 index 0000000..05807ec --- /dev/null +++ b/spec/spec_helper.rb @@ -0,0 +1,161 @@ +ENV["RAILS_ENV"] ||= "test" + +require 'dotenv' +Dotenv.load() + +# require "codeclimate-test-reporter" +require "simplecov" + +# CodeClimate::TestReporter.start +SimpleCov.start "rails" + +require File.expand_path("../../config/environment", __FILE__) +require "rspec/rails" +require "capybara/rspec" + +require "capybara/poltergeist" +Capybara.default_max_wait_time = 5 +Capybara.register_driver :poltergeist do |app| + Capybara::Poltergeist::Driver.new( + app, + timeout: 30, + # phantomjs_logger: File.open("/dev/null"), + phantomjs: Phantomjs.path + ) +end + +Capybara.javascript_driver = :poltergeist + +SELENIUM_HOST = ENV['SELENIUM_HOST'] +TEST_APP_HOST = ENV['TEST_APP_HOST'] +TEST_APP_PORT = ENV['TEST_APP_PORT'] + +Capybara.server_port = TEST_APP_PORT +Capybara.server_host = '0.0.0.0' +Capybara.app_host = "http://#{TEST_APP_HOST}:#{TEST_APP_PORT}" +Capybara.register_driver :selenium_remote do |app| + Capybara::Selenium::Driver.new( + app, + browser: :remote, + url: "http://#{SELENIUM_HOST}:4444/wd/hub", + desired_capabilities: Selenium::WebDriver::Remote::Capabilities.chrome + ) +end + +#Capybara.javascript_driver = :selenium +#Capybara.javascript_driver = :selenium_remote + +#print('selenium %s' % SELENIUM_HOST) +#print('port %d' % [TEST_APP_PORT]) +#print('host %s' % TEST_APP_HOST) + + + +# 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 +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 + + # Capybara + config.include Capybara::DSL + + # 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 + +# The settings below are suggested to provide a good initial experience +# with RSpec, but feel free to customize to your heart's content. + # 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 + config.order = "random" + config.use_transactional_fixtures = false + config.color = true + config.formatter = :documentation + config.infer_spec_type_from_file_location! + +# disabling calendar tests for now as they dont fit the new implementation anymore +=begin + config.before(:each) do + events_list_json = JSON.parse(File.read(Rails.root.join("spec/fixtures/google_calendar.json"))) + + allow(GoogleCalendar::Request).to receive(:events_list) do + GoogleCalendar::EventList.new(events_list_json, Time.zone.name) + end + end + # 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://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax + # - http://www.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