Helps

“How do I avoid timing problems while doing integration tests on single page apps?”

• Use a wait_until block with a selector which has not been cached.
• Use a wait_until block with a piece of javascript using evaluate_script which you expect to return when your page is finished loading.
• Use a wait_until block which waits for all AJAX to stop using $.ajaxStop().

Interesting

• Time.parse(invalid) will throw an exception, but
  Time.zone.parse(invalid) will return nil. Because Time.parse is part of the Ruby library while Time.zone is part of Rails.
• parallel_tests really does speed up your tests. It munges all the output together into an ugly mess though.

Interesting

• Date.today is not aware of the local timezone, but Date.yesterday is. Use Date.current or Time.zone.now instead.
• Hackathon May 12-13 for mobile game development. More info

Helps

“How do I not use VCR with Webmock in a spec?”

Use VCR.eject_cassette, see: docs

“Facebook now expires all tokens after 60 days. If you schedule a task with Facebook in the future it may use the expired token. Any solutions?”

Sadly there is nothing you can do. Send the user an email to re-auth.

“Good way to get replies on Twitter?”

Nope. Crawl thorough all your mentions, to get to your replies.

Interesting

• Problem: Select includes “*” by default, so selecting by specific column names does not work

If you write:

class Thing < ActiveRecord::Base
  has_many :posts
end

class Post < ActiveRecord::Base
  default_scope select(column_names - ['body'])
end

Thing.includes(:posts).all does the following for the posts query:

SELECT id, fk_column_id, column1, etc, posts.*
FROM posts
WHERE (pages.fk_column>in IN(1,2,3))

It takes the default select scope, but also appends posts.* to the end of it.

This is caused by the :select find_option in the find_associated_records inside of association_preload.rb. This is what it is now:

:select => preload_options[:select]
                || options[:select]
                || Arel::SqlLiteral.new("#{table_name}.*")

It seems like the third || case is not needed, since that is the default for any select and it causes the above behavior.

Joseph Palermo has filed a ticket with Lighthouse about this…