Interesting Things

• Rspec vs. Rails’ Test::Unit Gotcha: In a Controller test, Rspec provides access to that Controller’s attributes with assigns[:attr_name], or “array notation”, but Test::Unit does not. Both support assigns(:attr_name), or “method-call notation.”

Ask for Help

• “How should we migrate/upgrade database when we add new versions of assets, such as photos?” The consensus is that, for now, we’ll do it lazily: if an application (using our asset management plugin) needs a new version to be stored (perhaps we need a ‘tiny’ version…) when we will create them on-the-fly when requested rather than generate thousands of photos in one shot. If that has performance implications we’ll revisit that decision.
• Anyone want to be RailsConf roomies? Our sizable RailsConf contingent is going to try to share hotel rooms and such.
• We’re out of beer! A posse of those whom have been late to standup will make a run later today

Total Stand-up Meeting Time: 13:00 minutes

Interesting Things

• Rails Gotcha: If you name a Rails Migration class the same name as an ActiveRecord class, you will get a non-obvious “superclass mismatch” error.
• Javascript: Date.now() is not supported by Internet Explorer! Firefox is fine. If you use Date.now(), the cryptic and maddening “Object does not support this property or method” will be your reward. Cross-browser solution: new Date().getTime().
• Brown Bag Lunch today: Rails performance testing.

Ask for Help

• “Any JQuery experts in the house?” Unfortunately not, since most of us have used the Rails-favored Prototype libraries.
• If anyone has unbiased hosting service recommendations we would love to hear them. We’ve used several companies with mixed results.
• Rspec: “Does Rspec support all of the various route testing helpers that Rails’ Test::Unit extensions has?“. We think the answer is “yes” because Rspec extends Test::Unit, but we’ll have to research that one.

Total Stand-up Meeting Time: 15:00 minutes

Interesting Things

• One pair had this reinforced: you should not generate random data in your test case to be the subject of your assertions. In their case they were generating random usernames to test an “allowed characters” filter, but their tests would intermittently succeed or fail because the test was not deterministic.
• “A private declaration in a Helper doesn’t do jack crap!” Truer words were never spoken: private and protected declarations are not enforced in Rails View Helpers due to how that code is injected into View instances.
• A developer suggested that we attempt to do “RESTful CSS.” An explanation and debate is due soon.
• We are officially changing Wiki technologies from Twiki to Trac.
• Rails Gotcha: You can use Named routes to generate a URL for a link with my_named_route_url, but watch out: that URL is fully qualified! If you want a relative “URL”, use my_named_route_path. Example:

<code>
# config/routes.rb

login "/login", :controller => "user_management", :action => "login"
</code>

And in a any RHTML template:

<code>
login_url    # generates http://example.com/login

login_path   # generates /login
</code>

• People need to take more time to… blog! We have a laundry list of topics but no free time.

Total Stand-up Meeting Time: 17:00 minutes

Interesting Things

• Rails Observers: Observers need to be “primed” before they start working. Call Observer.instance before you start testing your Observers.
• Cookies in Rspec and Test::Unit: Cookie keys are not symbols, unlike many collection-like constructs in Rails; they are instead always Strings. Thus, use "cookie_name" not :cookie_name
• Rails reminder: ActiveRecord::create returns the stored object if successful, and the unsaved and invalid object in memory if the object could not be saved. If you want to know whether or not your save was successful, use ActiveRecord::save, which returns true when successful and false otherwise.
• And on a further note, a larger discussion should be had regarding when to use ActiveRecord::create, ActiveRecord::save, ActiveRecord::new, and ActiveRecord.dependent_object.build the latter of which is created when you have a has_many relationship with another ActiveRecord.

Total Stand-up Meeting Time: 20:00 minutes

Interesting Things

• Running initialization blocks per environment
  • Set an array in environment.rb to capture your procs that will do your post-initialization: POST_LOAD_BLOCKS = []
  • Now, in your environment-specific initialization files, you can do stuff like:
  • Then, back in environment.rb, after your environment has been initialized, loop over your array:

<code>
POST_LOAD_BLOCKS << Proc.new {
  a.runFoo
  b.runBar
}
</code>

Paydirt! These procs you’re appending to the POST_LOAD_BLOCKS array will get executed after your environment is completely initialized.

• Use silence_warnings to (you guessed it!) ‘silence’ warnings in Ruby – only pros should use it, and only when its clear exactly what you are doing!

Ask for Help

• None need today

Total Stand-up Meeting Time: ?

Just internal project-specific updates today!