You can overwrite some previous mocking by: expect(RestClient).to receive(:delete).and_call_original Or if it is wasn’t any kind of expectation, just a simple stub: allow(RestClient).to receive(:delete).and_call_original Remember there exists also expect_any_instance_of and allow_any_instance_of.
I had the same problem on Mac OS X Lion with FF 23. But the problem went away for me when I updated selenium-webdriver to 2.34.0 I added gem “selenium-webdriver”, “~> 2.34.0” into my Gemfile. bundle update selenium-webdriver bundle install Cucumber works fine with selenium now.
So the answer is No. before is equivalent to before :each, not before :all Test example. Update: Wow, this question is popular. To save your head from cognitive overload, I suggest you explicitly state :each or :all.
No, there is no and_not and no general negation operator, as discussed in https://github.com/rspec/rspec-expectations/issues/493 There is, however, a mechanism to define a negated version of an existing matcher, as described in http://www.rubydoc.info/github/rspec/rspec-expectations/RSpec/Matchers.define_negated_matcher, which you can use with and. The full set of compound matchers is documented at https://www.relishapp.com/rspec/rspec-expectations/v/3-4/docs/compound-expectations
When a before(:all) is defined in the RSpec.configure block it is called before each top level example group, while a before(:suite) code block is only called once. Here’s an example: RSpec.configure do |config| config.before(:all) { puts ‘Before :all’ } config.after(:all) { puts ‘After :all’ } config.before(:suite) { puts ‘Before :suite’ } config.after(:suite) { puts ‘After … Read more
Add to your Gemfile: group :development, :test do gem ‘rspec-rails’ end and run bundle install make sure that it is in both the :development and :test blocks. If you inadvertently put it only in the :test block, it will give the error above (that’s because by default you’re running in the development environment and rspec … Read more
You need to locate the hidden field and set its value. There are a couple ways, this is probably the simplest find(:xpath, “//input[@id=’my_hidden_field_id’]”).set “my value” If you’re executing a client_side script in production, you could just tell capybara to run it with a javascript-compliant driver page.execute_script(“$(‘hidden_field_id’).my_function()”)
There’s now a not very well documented method called expect_any_instance_of that handles the any_instance special case. You should use: expect_any_instance_of(Object).to receive(:subscribe) Google expect_any_instance_of for more info.
fill_in accepts the id as first parameter: fill_in ‘course_group_courses_attributes_2_name’, :with => ‘some text’
I like this much better. expect(page).to have_selector(‘input’, count: 12) https://github.com/jnicklas/capybara/blob/415e2db70d3b19b46a4d3d0fe62f50400f9d2b61/spec/rspec/matchers_spec.rb