Created
March 29, 2011 19:09
-
-
Save dhh/893027 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
describe "GET current" do | |
before do | |
@request.cookies['hidden_notices'] = "1,#{notices(:permanent).id}" | |
get :current, :format => 'js' | |
end | |
it { should respond_with(:success) } | |
it { should set_cookie(:hidden_notices).to("#{notices(:permanent).id}") } | |
it { should render_template('notices/current') } | |
end | |
end | |
# vs | |
test "GET current (or preferably an explanation WHY we are testing it)" do | |
@request.cookies['hidden_notices'] = "1,#{notices(:permanent).id}" | |
get :current, :format => 'js' | |
assert respond_with(:success) | |
assert_equal "#{notices(:permanent).id}", cookies[:hidden_notices] | |
assert_template 'notices/current' | |
end |
@mattwaynne: I don't think it's a matter of word choice at all. You're still replacing his opinion with lack of knowledge.
He's been quite clear about it. In fact, that's largely his point: it's heavily used because of a cargo cult. The question you'd have him ask is exactly the question to which his answer brought us all here.
@jrwest there is no need for the r
variable.
describe "GET current" do
it "does the same thing as your example" do
@request.cookies['hidden_notices'] = "1,#{notices(:permanent).id}"
get :current, :format => 'js'
response.should respond_with(:success) }
response.should set_cookie(:hidden_notices).to("#{notices(:permanent).id}") }
response.should render_template('notices/current') }
end
end
But in the end still it comes down to taste.
I can't take a design opinion seriously from the person who built rails.
Plus all the things that other people have pointed out about these examples being no way near equivalent.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@rubypanther you're right, it was off-hand of me to say "get it". What I meant was "appreciate why people find this a useful technique". RSpec isn't The Silver Bullet, but if it's working for a significant number of people, I think it's healthy for us to be curious about why that's the case.
Personally, I really find that whether I'm reading code out loud or in my head, the closer it is to the way I'd describe the behaviour in English, the less likely I am to miss a mistake.