assert_template against the same partial with different locals

[luisobo]

I have a view like this

<%= render :partial => 'widget', :locals => { :param => "10" } %>
<%= render :partial => 'widget', :locals => { :param => "20" } %>

Then in RSpec I'm doing this:

rendered.should render_template :partial => 'widget', :locals => { :param => "10" }
rendered.should render_template :partial => 'widget', :locals => { :param => "20" }

The first expectation is failing. It says something like expected "10", found "20". It looks like it's only saving the last partial and checking all my expectations against the last one.

The second expectation is passing.

The RSpec matcher render_template uses assert_template so the problem is the same there.

[frodsan]

@luisobo is this still an issue?

[kytrinyx]

@luisobo Can you provide a test application or reproduce the issue with test-unit?

[steveklabnik]

The rspec definition is here.

The rails definition is here.

I'm not familiar enough with how this is supposed to work. :/ I'm trying to make a rails app that demonstrates this now.

[steveklabnik]

I cannot for the life of me figure out how to make an integration test with test-unit.

Anyway, it would seem to me that the issue is here:

rails/actionpack/lib/action_controller/test_case.rb

Line 106 in 3cba6ee

actual_locals = @locals[expected_partial.to_s.sub(/^_/,'')]

This is going to write two values for the same key, which is why you're seeing the second only.

You could fix this by only writing one assertion per test. ;)

[senny]

@steveklabnik is this considered a bug? I could try to write up a patch. I added a failing test case to illustrate the problem.

[steveklabnik]

I think so.