Capybara/FeatureMethods conflicts with RSpec/DescribeClass in feature specs

[mvz]

rubocop-rspec should support rspec-rails' feature specs, however:

The following gives a RSpec/DescribeClass offense:

RSpec.describe 'user does foo', type: :feature do
  it 'succesfully foos the bar' do
    ...
  end
end

The following gives a Capybara/FeatureMethods offense:

RSpec.feature 'user does foo', type: :feature do
  scenario 'succesfully fooing the bar' do
    ...
  end
end

[Darhazer]

@mvz would #593 work for you?

[mvz]

@Darhazer I'm not sure. I was going to write a response based on reasoning, but I concluded I need to give this a try and see how it works out.

[mvz]

@Darhazer I'm afraid 75baab3 broke this cop completely for me, so it now never complains!

[mvz]

Ok, I've changed my code so the cop works for now and tested this. I'm afraid #593 doesn't really help, because I would want to enable all methods, so this would be no different from just disabling the cop for the spec/features directory.

Ideally, for me, rubocop-rspec would only allow the regular rspec methods in 'regular' specs, and only allow the feature methods in feature test.

[Darhazer]

Well, I guess you have to add the features spec folder to Exclude for the DescribeClass cop

[mvz]

@Darhazer Yes, that's what I did. An alternative for users who want the FeatureMethods cop enabled is to disable DescribeClass for the features spec folder.

[bquorning]

I am closing this issue, since the RSpec/Capybara/FeatureMethods cop was removed in #1876 / v3.0.0.