[rspec-users] best way to modify spec (the command-line tool)?

George Anderson george at benevolentcode.com
Fri Jan 4 11:31:07 EST 2008

"ghetto profiler": how appropriate for rails work these days.

You might ask on the rspec-devel list if you haven't already.


While you're waiting for a response, consider watching Zed's
interpretive piece in which he channels the King:


On 1/4/08, Giles Bowkett <gilesb at gmail.com> wrote:
> Hi all, where I work we've cooked up a kind of ghetto profiler for our
> specs. It basically just does this:
> time = Time.now
> # run the spec
> puts "woah! dude. long spec." if time > 1.second
> I'm simplifying here. I think the threshold is actually 0.1 seconds,
> and we use more precise language, and highlight the spec in red via
> terminal colors, etc.
> But the way it works is a bit ghetto. We just manually hacked it onto
> the Rails example groups (it's a Rails project) and then added a shell
> env var to turn it on and off.
> What's the cleanest way to implement this? Add a -profiling
> command-line flag to spec itself? Is there a single point of entry and
> exit for running individual specs that I can put the code around? It's
> currently manually hacked onto each example group individually and it
> seems a bit untidy.
> --
> Giles Bowkett
> Podcast: http://hollywoodgrit.blogspot.com
> Blog: http://gilesbowkett.blogspot.com
> Portfolio: http://www.gilesgoatboy.org
> Tumblelog: http://giles.tumblr.com
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


George Anderson

BenevolentCode LLC
O: (410) 461-7553
C: (410) 218-5185

george at benevolentcode.com

More information about the rspec-users mailing list