The conceptual difference is that you&#39;re usually testing a user story, and all interaction should be driven via the user interface.  That&#39;s where Capybara comes in.  A request spec is still testing the behavior of your application and doesn&#39;t have the expectation of readability that an acceptance test would have.  So, feature is there for the improved syntax for acceptance tests.

Technical differences include request specs wrap Rails integration tests, whereas feature specs don&#39;t. This means with request specs you can use methods get, post, put, delete and assert against response.  With feature specs you should drive all interaction through the browser and use methods like visit and assert against the page.


I&#39;d recommend reading the feature_spec.feature in the rspec-rails source code on github. I hope this helps.

I need to perform UPSERT / INSERT OR UPDATE against a SQLite Database.

There is the command INSERT OR REPLACE which in many cases can be useful. But if you want to keep your id&#39;s with autoincrement in place because of foreign keys, it does not work since it deletes the row, creates a new one and consequently this new row has a new ID.

This would be the table:

players - (primary key on id, user_name unique)


    |  id   | user_name |  age   |
    ------------------------------
    |  1982 |   johnny  |  23    |
    |  1983 |   steven  |  29    |
    |  1984 |   pepee   |  40    |




SQLite UPSERT / UPDATE OR INSERT

I am using a Windows Forms Application to monitor a directory and move the files dropped in it to another directory.

At the moment it will copy the file to another directory, but when another file is added it will just end with no error message. Sometimes it does copy two files before ending on the third.

Is this because I am using a Windows Form Application rather than a console app? Is there a way I can stop the program from ending and to keep watching the directory?

    private void watch()
    {
      this.watcher = new FileSystemWatcher();
      watcher.Path = path;
      watcher.NotifyFilter = NotifyFilters.LastAccess | NotifyFilters.LastWrite
                             | NotifyFilters.FileName | NotifyFilters.DirectoryName;
      watcher.Filter = &quot;*.*&quot;;
      watcher.Changed += OnChanged;
      watcher.EnableRaisingEvents = true;
    }

    private void OnChanged(object source, FileSystemEventArgs e)
    {
      //Copies file to another directory.
    }

    public void Dispose()
    {
      // avoiding resource leak
      watcher.Changed -= OnChanged;
      this.watcher.Dispose();
    }


Using FileSystemWatcher to monitor a directory

What is the conceptual difference between Rspec&#39;s [feature specs](https://www.relishapp.com/rspec/rspec-rails/v/2-13/docs/feature-specs/feature-spec) and [request specs](https://www.relishapp.com/rspec/rspec-rails/v/2-13/docs/request-specs/request-spec)?

From the feature spec docs:

&gt; Feature specs are high-level tests meant to exercise slices of functionality
through an application. They should drive the application only via its
external interface, usually web pages.

And for request specs:
&gt; Request specs provide a thin wrapper around Rails&#39; integration tests, and are
designed to drive behavior through the full stack, including routing
(provided by Rails) and without stubbing (that&#39;s up to you).
With request specs, you can:

&gt; - specify a single request
&gt; - specify multiple requests across multiple controllers
&gt; - specify multiple requests across multiple sessions

I know that feature specs use [Capybara](http://jnicklas.github.com/capybara/) and request specs do not. But that hardly merits different concepts.

RSpec: What is the difference between a feature and a request spec?

What is the conceptual difference between Rspec's <a href="https://www.relishapp.com/rspec/rspec-rails/v/2-13/docs/feature-specs/feature-spec" target="_blank" rel="noopener noreferrer">feature specs</a> and <a href="https://www.relishapp.com/rspec/rspec-rails/v/2-13/docs/request-specs/request-spec" target="_blank" rel="noopener noreferrer">request specs</a>?
From the feature spec docs:
> Feature specs are high-level tests meant to exercise slices of functionality
through an application. They should drive the application only via its
external interface, usually web pages.
And for request specs:
> Request specs provide a thin wrapper around Rails' integration tests, and are
designed to drive behavior through the full stack, including routing
(provided by Rails) and without stubbing (that's up to you).
With request specs, you can:
> - specify a single request
> - specify multiple requests across multiple controllers
> - specify multiple requests across multiple sessions
I know that feature specs use <a href="http://jnicklas.github.com/capybara/" target="_blank" rel="noopener noreferrer">Capybara</a> and request specs do not. But that hardly merits different concepts.

I&#39;m trying to run a query of about 50,000 records using ActiveRecord&#39;s `find_each` method, but it seems to be ignoring my other parameters like so:

    Thing.active.order(&quot;created_at DESC&quot;).limit(50000).find_each {|t| puts t.id }

Instead of stopping at 50,000 I&#39;d like and sorting by `created_at`, here&#39;s the resulting query that gets executed over the *entire* dataset:

    Thing Load (198.8ms)  SELECT &quot;things&quot;.* FROM &quot;things&quot; WHERE &quot;things&quot;.&quot;active&quot; = &#39;t&#39; AND (&quot;things&quot;.&quot;id&quot; &gt; 373343) ORDER BY &quot;things&quot;.&quot;id&quot; ASC LIMIT 1000

Is there a way to get similar behavior to `find_each` but with a total max limit and respecting my sort criteria?

ActiveRecord find_each combined with limit and order

I&#39;m attempting to follow the Hartl Rails Tutorial, and having trouble with the bundler gem.

When using the commands &#39;bundle install&#39; or &#39;bundle update&#39; I get the following output: 

&gt; Fetching source index from https://rubygems.org/
&gt; 
&gt; Could not fetch specs from https://rubygems.org/

I&#39;ve searched for this output, but did not find many related issues online. 

Maybe I have another gem that is interrupting bundler? I have little experience with rails at this point.

        source &#39;https://rubygems.org&#39;
    
    gem &#39;rails&#39;, &#39;3.2.12&#39;
    
    group :development do
      gem &#39;sqlite3&#39;, &#39;1.3.5&#39;
    end
    
    
    # Gems used only for assets and not required
    # in production environments by default.
    group :assets do
      gem &#39;sass-rails&#39;,   &#39;3.2.5&#39;
      gem &#39;coffee-rails&#39;, &#39;3.2.2&#39;
    
      gem &#39;uglifier&#39;, &#39;1.2.3&#39;
    end
    
    gem &#39;jquery-rails&#39;, &#39;2.0.2&#39;


**The solution for me was two parts:** I changed https to http, and that temporarily solved the issue. The second issue was that I think I had a bad install of ruby 2.0.0 even though I was using a fresh install of ruby 1.9.3. So I reinstalled ruby 2.0.0, and I could use bundle install with https.

Bundle Install could not fetch specs from https://rubygems.org/

Just to help other developers, because there is no similar question on SO.  

    div class=(is_active? ? &#39;active&#39; : &#39;inactive&#39;)
    div class=(&#39;active&#39; if is_active?)

slim dynamic conditional class

There&#39;s a strange issue with Rails 4 on Heroku.  When images are compiled they have hashes added to them, yet the reference to those files from within CSS don&#39;t have the proper name adjusted.  Here&#39;s what I mean.  I have a file called logo.png. Yet when it shows up on heroku it is viewed as:

    /assets/logo-200a00a193ed5e297bb09ddd96afb953.png

However the CSS still states:

    background-image:url(&quot;./logo.png&quot;);

The result: the image doesn&#39;t display.  Anybody run into this?  How can this be resolved?

Rails: How to reference images in CSS within Rails 4

Using Pry in Rails, when I hit a breakpoint in the code
    binding.pry

I want to know how I got here, who called  me, who called them, etc. But oddly I don&#39;t see that command. Does anyone know? 

Pry: show me the stack

I am testing the class which put on the console some messages (with puts, p warnings and etc.).  I am just wondering if there is any ability to suppress this output during RSpec tests ?

Suppress console output during RSpec tests

[The before and after hook documentation on Relish](https://www.relishapp.com/rspec/rspec-core/v/2-13/docs/hooks/before-and-after-hooks) only shows that `before(:suite)` is called prior to `before(:all)`.

When should I use one over the other?

In RSpec, what&#39;s the difference between before(:suite) and before(:all)?

So I am currently writing a test for a controller in an existing controller that just didn&#39;t have one before. What I want to test is a redirect that happens when someone is not allowed to edit something vs someone that is allowed to edit it.

the controller action being edit 

    def edit
      if !@scorecard.reviewed? || admin?
        @company = @scorecard.company
        @custom_css_include = &quot;confirmation_page&quot;
      else
        redirect_to :back
      end
    end

So if a scorecard has been reviewed then only an admin can edit that score.
The routes for that controller..

    # scorecards
    resources :scorecards do
      member do
        get &#39;report&#39;
      end
      resources :inaccuracy_reports, :only =&gt; [:new, :create]
    end

and finally the test

      require &#39;spec_helper&#39;
 
      describe ScorecardsController do

        describe &quot;GET edit&quot; do
          before(:each) do
            @agency = Factory(:agency)
            @va = Factory(:va_user, :agency =&gt; @agency)
            @admin = Factory(:admin)
            @company = Factory(:company)
            @scorecard = Factory(:scorecard, :level =&gt; 1, :company =&gt; @company, :agency =&gt; @agency, :reviewed =&gt; true)
            request.env[&quot;HTTP_REFERER&quot;] = &quot;/scorecard&quot;
          end

          context &quot;as a admin&quot; do
            before(:each) do
              controller.stub(:current_user).and_return @admin
            end

            it &quot;allows you to edit a reviewed scorecard&quot; do
              get &#39;edit&#39;, :id =&gt; @scorecard.id
              response.status.should be(200)
            end
          end
    
          context &quot;as a va_user&quot; do
            before(:each) do
            controller.stub(:current_user).and_return @va
          end

    	  it &quot;does not allow you to edit a reviewed scorecard&quot; do
    	    get &#39;edit&#39;, :id =&gt; @scorecard.id
    	    response.should redirect_to :back
          end
        end
      end
    end

so a va when trying to edit a reviewed score will be redirected back, where an admin won&#39;t.

but when running this through rspec I get

    ScorecardsController
      GET edit
        as a admin
          allows you to edit a reviewed scorecard
        as a va_user
          does not allow you to edit a reviewed scorecard (FAILED - 1)

    Failures:

      1) ScorecardsController GET edit as a va_user does not allow you to edit a reviewed scorecard
         Failure/Error: response.should redirect_to :back
       Expected response to be a redirect to &lt;/scorecard&gt; but was a redirect to &lt;http://test.host/&gt;
         # ./spec/controllers/scorecards_controller_spec.rb:33:in `block (4 levels) in &lt;top (required)&gt;&#39;

    Finished in 0.48517 seconds
    2 examples, 1 failure

so I don&#39;t know if its working or not since I set the `request.env[&quot;HTTP_REFERER&quot;] = &quot;/scorecard&quot;` as the place that should be the `:back` as it where. or am I missing the idea all together looking at &lt;a href=&quot;http://httpstatus.es/&quot;&gt;httpstatus&lt;/a&gt; there are the 300 responses that I could use but I wouldn&#39;t know where to start?

any help would be awesome 

&lt;h2&gt;EDIT&lt;/h2&gt;

I could test it by doing it like this
    
    ...
    response.status.should be(302)

but I got the idea from this &lt;a href=&quot;https://stackoverflow.com/questions/6040479/rspec-testing-redirect-to-back&quot;&gt;question&lt;/a&gt; and it sounds like this could be powerful as it specifies the url redirected to.

Anyone have a working test like this?

Rails/Rspec - testing a redirect in the controller

Given that I have a `Personable` concern in my Rails 4 application which has a `full_name` method, how would I go about testing this using RSpec?

**concerns/personable.rb**

    module Personable
      extend ActiveSupport::Concern
    
      def full_name
        &quot;#{first_name} #{last_name}&quot;
      end
    end



How to Test a Concern in Rails

&lt;!-- language-all: ruby --&gt;

Yes, I know, that testing private methods it&#39;s not a good idea (and I
read this thread - http://www.ruby-forum.com/topic/197346 - and some
others)

But how can I test the following code?

I use xmpp4r. In my public method `#listen` I start receive jabber
messages like so:

    def listen
      @client.add_message_callback do |m|
        do_things_with_message(m)
      end
    end

    private
    def do_things_with_message(m)
      #
    end

`#add_message_callback` - runs block, when message come (in different thread)

So, testing `#listen` method it&#39;s difficult and it more testing xmpp4r
than my `#do_things_with_message`

How to do all right and test `#do_things_with_message`?:)
(http://www.ruby-forum.com/topic/197346#859664)

*Refactor private methods to a new object* essentialy would be as I making them a public (and class with one method - it&#39;s senselessly

**EDIT:**
This is more a theoretical question about clean code and the correct tests.
In my first link people argue that the test private methods poorly.
I don&#39;t want cheat with `#send`, but also I don&#39;t see any viable ways to refactor

Testing private method in Ruby (rspec)

The following piece of code works as expected:

    Object.any_instance.should_receive(:subscribe)

But when using the new rspec expectation it does not work:

    expect(Object.any_instance).to receive(:subscribe)

The error is:

    expected: 1 time with any arguments
    received: 0 times with any arguments

How can I make this work with expect() to receive?


Object.any_instance should_receive vs expect() to receive

I am doing the Rails Tutorial for the second time. When I enter this 

    rails generate integration_test static_pages

I get `spec/rails_helper.rb` and `spec/spec_helper.rb` instead of just `spec/spec_helper.rb`

Now when I run my tests, they are longer (more &quot;verbose&quot;) and slower than when I did this last time. 
I am wondering what the difference between the two files is, and if I did something wrong.
Also, is there a way to get rid of the `rails_helper.rb` file without messing everything up?

How is spec/rails_helper.rb different from spec/spec_helper.rb? Do I need it?

After upgrading a Rails app to Rails 5, running RSpec tests gives me the following error:

    rails aborted!
    ActiveRecord::NoEnvironmentInSchemaError: 

    Environment data not found in the schema. To resolve this issue, run: 

	    bin/rails db:environment:set RAILS_ENV=test

However, that `bin` does not exist and I can&#39;t seem to generate it with `bundle binstubs rails` or with `rake rails:update:bin`.

I have also tried:
    
    rails db:environment:set RAILS_ENV=test
    rake db:environment:set RAILS_ENV=test

There is a related issue on Github [here](https://github.com/rails/rails/issues/23279).

How can I address this error?

Rails 5, Rspec: Environment data not found in the schema

I&#39;m using Rails 5, and Devise 3.5.1.

Going through a nice (older) book about creating/testing an API, which uses Devise authentication. It was written before Rails 5, so I chose not to use the new api-only version.

Here&#39;s my test...

    #/spec/controllers/api/v1/users_controller_spec.rb    

    require &#39;rails_helper&#39;
    
    describe Api::V1::UsersController, :type =&gt; :controller do
        before(:each) { request.headers[&#39;Accept&#39;] = &quot;application/vnd.marketplace.v1&quot; }
        describe &quot;GET #show&quot; do
            before(:each) do
                @user = FactoryGirl.create :user
                get :show, params: {id: @user.id}, format: :json
            end
            it &quot;returns the information about a reporter on a hash&quot; do
                user_response = JSON.parse(response.body, symbolize_names: true)
                expect(user_response[:email]).to eql @user.email
            end
            it { should respond_with 200 }
        end
    end

And here&#39;s a completely unexpected RSpec error

    Devise::MissingWarden:
           Devise could not find the `Warden::Proxy` instance on your request environment.
           Make sure that your application is loading Devise and Warden as expected and that the `Warden::Manager` middleware is present in your middleware stack.
           If you are seeing this on one of your tests, ensure that your tests are either executing the Rails middleware stack or that your tests are using the `Devise::Test::ControllerHelpers` module to inject the `request.env[&#39;warden&#39;]` object for you.


So I go here - http://www.rubydoc.info/gems/devise/Devise/Test/ControllerHelpers

and tried this -&gt; **include Devise::Test::ControllerHelpers**

which didn&#39;t help because the file `controller_helpers.rb` is nowhere in my project

What did I miss here?

Thanks

Why is my RSpec not loading Devise::Test::ControllerHelpers?

I have simple action show 

    def show
      @field = Field.find_by(params[:id])
    end

and i want write spec for it 

    require &#39;spec_helper&#39;
    
    RSpec.describe FieldsController, type: :controller do
    
        let(:field) { create(:field) }
    
      it &#39;should show field&#39; do
        get :show, id: field
        expect(response.status).to eq(200)
      end
    end


but I have got an error

    Failure/Error: get :show, id: field
     
     ArgumentError:
       unknown keyword: id

How to fix it?

Content Type	Original Author	Original Content on Stackoverflow
Question	harm	View Question on Stackoverflow
Solution 1 - Ruby on-Rails	Richard Jordan	View Answer on Stackoverflow

RSpec: What is the difference between a feature and a request spec?

Ruby on-Rails Problem Overview

Ruby on-Rails Solutions

Solution 1 - Ruby on-Rails

Using FileSystemWatcher to monitor a directory

SQLite UPSERT / UPDATE OR INSERT

Attributions