Pivotal Labs

Main menu

Skip to primary content
Skip to secondary content
  • About
  • Case Studies
  • Team
    • Executives
    • Locations
      • San Francisco (HQ)
      • Boston
      • Boulder
      • Denver
      • London
      • Los Angeles
      • New York
  • Community
    • Blogs
    • Tech Talks
    • Events
  • Careers
    • Lifestyle
    • Principles & Practices
    • Benefits
    • FAQ
    • Apply
  • Contact
    • Press Room
    • Press Releases
    • In The News
    • Press Kit
  • All
  • Labs
  • Standup
  • Tracker

Standup 7/27/2009: Testing Partial Locals

Jacob Maine
Monday, July 27, 2009

Ask for Help

“What’s the best way to test that a controller (a) renders a partial and (b) passes the partial the right locals?”

Mocking render_template and the locals ends up mocking too much of the request cycle. Ideally, we’d like something like:

response.should render_partial("item", :locals => {:item => assigns[:item]})

“Hpricot breaks with xml elements named param. Any suggestions?”

Works if we replace Hpricot with Nokogiri, so that may be the way to go.

Interesting Things

  • A follow up on the problems using Fixture Scenarios with Rails 2.3.2: The fixture are loading twice, although it’s not clear why. The second run barfs with a syntax error. Perhaps the first run doesn’t properly close the fixture file?
  • Raising the timeout fixed issues with S3 uploads over slow connections. It might also be more efficient. The timeout could stop a 90% complete upload, then kick off a retry (the gem has a 3 retry policy), which further clogs the tubes.

Update: The Hpricot problem is with elements named param, not params as I originally stated.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter

One comment

  1. Daniel DeLeo says:

    Of interest: _Why is hard to decode, but seems like he’s abdicating to Nokogiri:

    http://twitter.com/_why/status/2484099316

    July 27, 2009 at 6:18 pm

Add New Comment Cancel reply

Your email address will not be published.

Jacob Maine

Jacob Maine
Boston

Recent Posts

  • Standup 2012/2/1: Speed kills
  • Standup 2012/1/31: The bleeding edge
  • Standup 1/30/2012: It’s all about sharing
Subscribe to Jacob's Feed

Author Topics

agile (14)
testing (6)
rails (2)
prototype (2)
jruby (1)
hpricot (1)
  • About
  • Case Studies
  • Team
  • Community
  • Careers
  • Contact
  • Labs
  • Events

Contact Us

contact@pivotallabs.com
+1 415-77-PIVOT
TwitterLinkedInFacebook

Pivotal Tracker

Tracker is the award-winning agile project management tool that enables real-time collaboration around a shared, prioritized backlog.
Visit pivotaltracker.com >