More wrong behavior on RSpec expect change count with destroy

Question

I'm making an app where people can create jobs, but can only destroy the jobs they've created. I know that my app lets people destroy jobs because I can test it manually, but RSpec is lagging behind.

Here's the relevant test:

jobs_controller_spec.rb

require 'spec_helper'

describe JobsController do
  let!(:user) { FactoryGirl.create(:user) }
  let!(:job) { FactoryGirl.create(:job, user: user) }
  let!(:wrong_user) { FactoryGirl.create(:user, email: "wrong@example.com") }
  let!(:wrong_job) { FactoryGirl.create(:job, user: wrong_user) }

  [...]

  describe "correct user control" do
    before { sign_in user }
    describe "users can only delete their own jobs" do
      it "should not change job count" do
        expect do
          delete :destroy, id: wrong_job.id
        end.to_not change(Job, :count)
      end
    end
    describe "users can delete their own jobs" do
      it "should decrease job count" do
        expect do
          delete :destroy, id: job.id
            end.to change(Job, :count).by(-1)
          end
        end
      end
    end

Here's the failing test:

1) JobsController correct user control users can delete their own jobs should decrease job count
     Failure/Error: expect do
       count should have been changed by -1, but was changed by 0
     # ./spec/controllers/jobs_controller_spec.rb:41:in `block (4 levels) in <top (required)>'

jobs_controller.rb

class JobsController < ApplicationController
  skip_before_action :require_signin, only: [:index, :show]
  skip_before_action :correct_user, only: [:index, :show, :new, :create]
  before_action :set_job, only: [:show, :edit, :update, :destroy]

  [...]

  def destroy
    @job.destroy
    respond_to do |format|
      format.html { redirect_to jobs_url }
      format.json { head :no_content }
    end
  end

  private
    def set_job
      @job = Job.find(params[:id])
    end

  def job_params
    params.require(:job).permit(:title, :org, :internship, :postdate, :filldate, :location, :link, :description)
  end
end

application_controller.rb

class ApplicationController < ActionController::Base
  protect_from_forgery with: :exception
  before_filter :require_signin
  before_filter :correct_user

  include SessionsHelper

  private
    def require_signin
      unless signed_in?
        store_location
        redirect_to signin_url, notice: "Please sign in."
      end
    end

    def correct_user
      @job = current_user.jobs.find_by(id: params[:id])
      redirect_to root_url if @job.nil?
    end
end

rake routes

Prefix Verb   URI Pattern              Controller#Action
       jobs GET    /jobs(.:format)          jobs#index
            POST   /jobs(.:format)          jobs#create
    new_job GET    /jobs/new(.:format)      jobs#new
   edit_job GET    /jobs/:id/edit(.:format) jobs#edit
        job GET    /jobs/:id(.:format)      jobs#show
            PATCH  /jobs/:id(.:format)      jobs#update
            PUT    /jobs/:id(.:format)      jobs#update
            DELETE /jobs/:id(.:format)      jobs#destroy
[...]

Answer 1

The solution is to pass no_capybara: true to sign_in. Capybara doesn't work with controller tests, so one can't use capybara to manage the sign in process.

Thanks to Patrick Brinich-Langlois for the solution.

Answer 2

As Peter Alfvin points out, if there is authentication in controller specs you have to setup a session and pass it as third parameter, for example:

...
let(:some_user) { User.create }

def valid_session
  { user_id: some_user.id }
end

describe "DELETE destroy" do
  it "destroys the requested job" do
    job = Job.create! valid_attributes
    expect {
      delete :destroy, { :id => job.to_param }, valid_session
    }.to change(Job, :count).by(-1)
  end
end