Rails Envy Podcast - Episode #044: 08/27/2008

I hear that those Rspec it_should_behave_like articles are awesome (especially the one by Ed Spencer), but those Rails Envy fools broke the link. Gorramit :(

For your next fix of it_should_* goodness check out Matthew Bass’s rspec validation expectations (http://github.com/edspencer/rspec_validation_expectations), which lets you do this:

describe User do it_should_validate_presence_of :first_name, :last_name, :email it_should_validate_numericality_of :zip it_should_validate_uniqueness_of :email it_should_validate_inclusion_of :gender, :in => %w(Male Female) end

1. tests that User.count increases by 1 it_should_be_createable :with => {:first_name => ‘Ed’, :last_name => ‘The Duck’, :email => ‘a@b.com’}

it_should_belong_to :employer
it_should_have_many :friends, :romans, :countrymen
it_should_have_one  :account
it_should_have_and_belong_to_many :comments

Pretty neat, no? I’ve been playing with some more stuff like this to get your model and controller specs even prettier - article part deux coming up later this week!

Sorry I linked to my fork of rspec_validation_expectations - the real one’s at http://github.com/pelargir/rspec_validation_expectations.

Also - dude, we can’t paste no RSpec in the comments?

should behave like: http://www.robbyonrails.com/articles/2008/08/19/rspec-it-should-behave-likehttp://edspencer.net/2008/08/drying-up-your-crud-controller-rspecs.html

says: The page you are looking for is temporarily unavailable. Please try again later.

And I hear that rails can’t scale…

NeverBlock is lookin’ good. Not as good as this soup I’m about to eat, though. God I love soup. Gonna put some crackers in this soup. If your podcast were a soup, it would be, like, a delicious soup. But not as delicious as this soup I’m about to eat, sorry.

JRuby connection pools are useful even without multithreaded Rails.

You normally run multiple Rails runtimes running the same app inside a single glassfish instance (to get around AR and Rails single threadedness). This is all done for you when you build the WARfile.

A Glassfish instance is more like a Mongrel cluster than a single Rails process. (which is itself clusterable. More scalability than a mermaids booty)