search for: benburkert

...automatically run code metrics in the same way as autotest. It''s runs rcov, flog, and saikuro right now, and works with rspec and rails. It''s hosted at rubyforge: http://rubyforge.org/projects/autometric/ I''ve got a post on how to configure it with growl: http://benburkert.com/2007/11/9/introducing-autometric I''m hoping to get Heckle working soon. -Ben

Is it possible to access the described class in a shared behavior? I''m trying to do something like this: describe "Siberian feline", :shared => true do described_class_instance_as :feline, :name => "fluffy", :breed => "Siberian" # or maybe before(:all) do @feline = described_class.new(:name => "fluffy", :breed =>

...a "sync" job with a local repo pulling from rubyforge and pushing to github. I also don''t know of (or see why they would provide) options to do this automatically from either rubyforge or github. [1] http://github.com/thewoolleyman/cruisecontrolrb/network [2] http://github.com/benburkert/cruisecontrolrb/network

I just ran into this error after updating rails and the rspec_on_rails plugin (both are on edge): /Users/ben/Work/wizzdl/vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:263:in `load_missing_constant'': uninitialized constant ActionView::Helpers::PaginationHelper (NameError) from /Users/ben/Work/wizzdl/vendor/rails/activerecord/

I have my application happily generating UUID primary keys using the uuidtools gem. But the auto-generated specifications created by "script/generate rspec_scaffold...", etc, assume that one is using a sequential integer primary key. For those who have hit this same issue, is it just a matter of rewriting the auto-generated specifications to take this into account, or does one have to