Capybara / rspec: should GET / PUT tests be in different files?

I am following Ruby on Rails Tutorial and now I need to write tests for authorization code like. making sure users can only edit their profile.

There are two steps to test. One of them is to prevent the user from accessing the edit page of other users' profile. This simple, simple "special" test in capybara.

But I also want to test the PUT action so that the user cannot manually submit a PUT request without going through the edit page. From what I've read, this should be done as a test of the rspec request.

Now my question is, do I need to support them in different categories? (spec / features vs spec / requests)? This is wrong because the two scenarios are closely related. How are tests like this usually done in Rails?

For example,

describe "as wrong user" do
  let(:user) { FactoryGirl.create(:user) }
  let(:wrong_user) { FactoryGirl.create(:user, email: "wrong@example.com") }
  before { sign_in user }

  describe "visiting Users#edit page" do
    before { visit edit_user_path(wrong_user) }
    it { should_not have_selector('title', text: full_title('Edit user')) }
  end

  describe "submitting a PUT request to the Users#update action" do
    before { put user_path(wrong_user) }
    specify { response.should redirect_to(root_path) }
  end
end

      

        
        
        
      

    

The second test does not work in capybara 2.x as "put" is no longer supported. It should be a request. And now I need to write a second sign_in method, since the current one uses methods available only for testing functions. Smells like a lot of code duplication.

======== my solution ========

After figuring out how to enter the query test, thanks to Paul Fioravanti,

    before do
      post sessions_path, email: user.email, password: user.password
      cookies[:remember_token] = user.remember_token
    end

      

        
        
        
      

    

I changed all tests to request tests. So I don't need to split them into different files. Paul's solution will also work, although I think it's cleaner.

describe 'authorization' do
  describe 'as un-signed-in user' do
    let(:user) { FactoryGirl.create(:user) }

    describe 'getting user edit page' do
      before { get edit_user_path(user) }

      specify { response.should redirect_to(signin_path) }
    end

    describe 'putting to user update page' do
      before { put user_path(user) }

      specify { response.should redirect_to(signin_path) }
    end
  end

  describe 'as wrong user' do
    let(:user) { FactoryGirl.create(:user) }
    let(:wrong_user) { FactoryGirl.create(:user, email: 'wrong@example.com') }

    before do
      post sessions_path, email: user.email, password: user.password
      cookies[:remember_token] = user.remember_token
    end

    describe 'getting user edit page' do
      before { get edit_user_path(wrong_user) }

      specify { response.should redirect_to(root_path) }
    end

    describe 'putting to user update page' do
      before { put user_path(wrong_user) }

      specify { response.should redirect_to(root_path) }
    end
  end
end