Commit 2cc6a7513f0fffdd2191957dfe9519b01f59ff3b

Authored by Daniel Damasceno
1 parent 4d9ed179
Exists in elasticsearch_api

Removing spec to change tests for elasticsearch

spec/models/community_spec.rb
@@ -1,23 +0,0 @@ @@ -1,23 +0,0 @@
1 -require 'rails_helper'  
2 -require 'rake'  
3 -require 'elasticsearch/extensions/test/cluster/tasks'  
4 -  
5 -describe Community, type: :model, elasticsearch: true do  
6 - before do  
7 - @environment = Environment.default  
8 - @environment.enabled_plugins = ['ElasticsearchPlugin']  
9 - @environment.save!  
10 -  
11 - @community = Community.new(name: "Debian")  
12 - @community.save!  
13 - _start = Time.new  
14 - Article.import  
15 - sleep 4  
16 - p Article.__elasticsearch__.client.cluster.health  
17 - end  
18 -  
19 - it "assert true" do  
20 - Article.__elasticsearch__.search({}).records.to_a  
21 - expect(true).to be true  
22 - end  
23 -end  
spec/rails_helper.rb
@@ -1,52 +0,0 @@ @@ -1,52 +0,0 @@
1 -# This file is copied to spec/ when you run 'rails generate rspec:install'  
2 -ENV['RAILS_ENV'] ||= 'test'  
3 -require File.expand_path('../../config/environment', __FILE__)  
4 -# Prevent database truncation if the environment is production  
5 -abort("The Rails environment is running in production mode!") if Rails.env.production?  
6 -require 'spec_helper'  
7 -require 'rspec/rails'  
8 -# Add additional requires below this line. Rails is not loaded until this point!  
9 -  
10 -# Requires supporting ruby files with custom matchers and macros, etc, in  
11 -# spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are  
12 -# run as spec files by default. This means that files in spec/support that end  
13 -# in _spec.rb will both be required and run as specs, causing the specs to be  
14 -# run twice. It is recommended that you do not name files matching this glob to  
15 -# end with _spec.rb. You can configure this pattern with the --pattern  
16 -# option on the command line or in ~/.rspec, .rspec or `.rspec-local`.  
17 -#  
18 -# The following line is provided for convenience purposes. It has the downside  
19 -# of increasing the boot-up time by auto-requiring all files in the support  
20 -# directory. Alternatively, in the individual `*_spec.rb` files, manually  
21 -# require only the support files necessary.  
22 -#  
23 -# Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }  
24 -  
25 -# Checks for pending migrations before tests are run.  
26 -# If you are not using ActiveRecord, you can remove this line.  
27 -ActiveRecord::Migration.maintain_test_schema!  
28 -  
29 -RSpec.configure do |config|  
30 - # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures  
31 - config.fixture_path = "#{::Rails.root}/spec/fixtures"  
32 -  
33 - # If you're not using ActiveRecord, or you'd prefer not to run each of your  
34 - # examples within a transaction, remove the following line or assign false  
35 - # instead of true.  
36 - config.use_transactional_fixtures = true  
37 -  
38 - # RSpec Rails can automatically mix in different behaviours to your tests  
39 - # based on their file location, for example enabling you to call `get` and  
40 - # `post` in specs under `spec/controllers`.  
41 - #  
42 - # You can disable this behaviour by removing the line below, and instead  
43 - # explicitly tag your specs with their type, e.g.:  
44 - #  
45 - # RSpec.describe UsersController, :type => :controller do  
46 - # # ...  
47 - # end  
48 - #  
49 - # The different available types are documented in the features, such as in  
50 - # https://relishapp.com/rspec/rspec-rails/docs  
51 - config.infer_spec_type_from_file_location!  
52 -end  
spec/spec_helper.rb
@@ -1,96 +0,0 @@ @@ -1,96 +0,0 @@
1 -# This file was generated by the `rails generate rspec:install` command. Conventionally, all  
2 -# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.  
3 -# The generated `.rspec` file contains `--require spec_helper` which will cause  
4 -# this file to always be loaded, without a need to explicitly require it in any  
5 -# files.  
6 -#  
7 -# Given that it is always loaded, you are encouraged to keep this file as  
8 -# light-weight as possible. Requiring heavyweight dependencies from this file  
9 -# will add to the boot time of your test suite on EVERY test run, even for an  
10 -# individual file that may not need all of that loaded. Instead, consider making  
11 -# a separate helper file that requires the additional dependencies and performs  
12 -# the additional setup, and require it from the spec files that actually need  
13 -# it.  
14 -#  
15 -# The `.rspec` file also contains a few flags that are not defaults but that  
16 -# users commonly want.  
17 -#  
18 -# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration  
19 -require 'rake'  
20 -require 'elasticsearch/extensions/test/cluster/tasks'  
21 -  
22 -RSpec.configure do |config|  
23 -  
24 - # rspec-expectations config goes here. You can use an alternate  
25 - # assertion/expectation library such as wrong or the stdlib/minitest  
26 - # assertions if you prefer.  
27 - config.expect_with :rspec do |expectations|  
28 - # This option will default to `true` in RSpec 4. It makes the `description`  
29 - # and `failure_message` of custom matchers include text for helper methods  
30 - # defined using `chain`, e.g.:  
31 - # be_bigger_than(2).and_smaller_than(4).description  
32 - # # => "be bigger than 2 and smaller than 4"  
33 - # ...rather than:  
34 - # # => "be bigger than 2"  
35 - expectations.include_chain_clauses_in_custom_matcher_descriptions = true  
36 - end  
37 -  
38 - # rspec-mocks config goes here. You can use an alternate test double  
39 - # library (such as bogus or mocha) by changing the `mock_with` option here.  
40 - config.mock_with :rspec do |mocks|  
41 - # Prevents you from mocking or stubbing a method that does not exist on  
42 - # a real object. This is generally recommended, and will default to  
43 - # `true` in RSpec 4.  
44 - mocks.verify_partial_doubles = true  
45 - end  
46 -  
47 -# The settings below are suggested to provide a good initial experience  
48 -# with RSpec, but feel free to customize to your heart's content.  
49 -=begin  
50 - # These two settings work together to allow you to limit a spec run  
51 - # to individual examples or groups you care about by tagging them with  
52 - # `:focus` metadata. When nothing is tagged with `:focus`, all examples  
53 - # get run.  
54 - config.filter_run :focus  
55 - config.run_all_when_everything_filtered = true  
56 -  
57 - # Allows RSpec to persist some state between runs in order to support  
58 - # the `--only-failures` and `--next-failure` CLI options. We recommend  
59 - # you configure your source control system to ignore this file.  
60 - config.example_status_persistence_file_path = "spec/examples.txt"  
61 -  
62 - # Limits the available syntax to the non-monkey patched syntax that is  
63 - # recommended. For more details, see:  
64 - # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax  
65 - # - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/  
66 - # - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching  
67 - config.disable_monkey_patching!  
68 -  
69 - # Many RSpec users commonly either run the entire suite or an individual  
70 - # file, and it's useful to allow more verbose output when running an  
71 - # individual spec file.  
72 - if config.files_to_run.one?  
73 - # Use the documentation formatter for detailed output,  
74 - # unless a formatter has already been configured  
75 - # (e.g. via a command-line flag).  
76 - config.default_formatter = 'doc'  
77 - end  
78 -  
79 - # Print the 10 slowest examples and example groups at the  
80 - # end of the spec run, to help surface which specs are running  
81 - # particularly slow.  
82 - config.profile_examples = 10  
83 -  
84 - # Run specs in random order to surface order dependencies. If you find an  
85 - # order dependency and want to debug it, you can fix the order by providing  
86 - # the seed, which is printed after each run.  
87 - # --seed 1234  
88 - config.order = :random  
89 -  
90 - # Seed global randomization in this process using the `--seed` CLI option.  
91 - # Setting this allows you to use `--seed` to deterministically reproduce  
92 - # test failures related to randomization by passing the same `--seed` value  
93 - # as the one that triggered the failure.  
94 - Kernel.srand config.seed  
95 -=end  
96 -end