Interesting question; something that I want to know more about as well…. So dug in a bit, and here is what I uncovered: Thoughtbot style guide dictum about let, etc. In an earlier version of the style guide, there’s more to that statement: Avoid its, let, let!, specify, subject, and other DSLs. Prefer explicitness and … Read more
It seems that running bundle exec rake -t will work. Per bundler.io http://bundler.io/man/bundle-exec.1.html I suggest adding bundle exec to ensure that we are using the Gem specified in the current context. Also see this SO post. What does bundle exec rake mean?
I also experienced this issue when replacing chromedriver-helper with webdrivers, however updating Capybara to the latest version (3.18.0) resolved it.
ANSWER: I’m self answering my question here. rake spec will take the SPEC_OPTS environment variable. rake spec SPEC_OPTS=”–format documentation”
Ok so this is how I do, I don’t pretend to strictly follow the best practices, but I focus on precision of my tests, clarity of my code, and fast execution of my suite. So let take example of a UserController 1- I do not use FactoryGirl to define the attributes to post to my … Read more
expect(page).to have_content(“my-text”, count: 2) will do what you want in modern versions of Capybara, not sure if that will work in 2.1 but worth trying (2.1 is over 2 years old now) Update: In Capybara 3.19+ this can also now be written expect(page).to have_content(“my-text”).twice
Solved it with help from my colleague. Turns out that the spec files have to be named with a _spec suffix, and bundle exec rspec spec works. I name the spec file with a test_ prefix previously. Was using bundler 1.3.5 and rspec 2.14.1
From the documentation, the expected redirect path can match a regex: expect(response).to redirect_to %r(\Ahttp://example.com) To verify the redirect location’s query string seems a little bit more convoluted. You have access to the response’s location, so you should be able to do this: response.location # => http://example.com?foo=1&bar=2&baz=3 You should be able to extract the querystring params … Read more
In order to use these helpers you have to include them into your tests. You can do this by either including it into single test suite: describe MyClass do include ActiveSupport::Testing::TimeHelpers end or globally: RSpec.configure do |config| config.include ActiveSupport::Testing::TimeHelpers end
Here’s the commit which adds the feature to rspec – This was on May 25 2008. With this you can do A.any_instance.stub(do_something: 23) However, the latest gem version of rspec (1.1.11, October 2008) doesn’t have this patch in it. This ticket states that they yanked it out for maintenance reasons, and an alternative solution hasn’t … Read more