rspec_rails_4
rspec_rails_4 copied to clipboard
Everyday Rails Testing with RSpec (Rails 4.0 Edition)
You add 'rspec-collection_matchers' gem to `group :development, :test` but it should be okay even if adding to test group only, correct?
Hello, I did git checkout -b remotes/origin/01-untested and want to adapt the gem file according to chapter 2. But everything is already in place in the gem file ? Roelof
In Ch.5 p.50 and p.57, both describe "PATCH#update" but they have different examples.
In be_named matcher, eq is used but it fails with message "ArgumentError: wrong number of arguments (1 for 0)". [According to the RSpec document](https://www.relishapp.com/rspec/rspec-expectations/v/2-3/docs/custom-matchers/define-matcher), it should be "==". ``` ruby...
Minor typo on Line 2 (siuation should be spelt as "situation", with a "t")
Page 53 implies that PATCH replaces PUT from and inclusive of Rails 4 onwards, however subsequent examples in the book still use PUT instead of PATCH (i.e. Page 63).
> Technically speaking, we could also use the more concise `expect(...).to be` and `expect(...).to_not be` as well. I am not sure what this sentence means. Do you mean you can...
Hi Aaron, Many thanks for your continued update to the book. I have a request for you. I don't want to re-read the full book to keep up with the...
In ch.12 (Toward RSpec 3), a word "siuation" exists. It should be "situation". “As noted, this is a semantic change intended to differentiate between a “truthy” value (that is, not...
A small typo on this page. The box says: > Enabling this configuration will cause every example in our suite to **fix** until the > Capybara- related warnings are addressed...