Profiling a cucumber test (ruby/rails)

Question

Profiler/profiling related issue with Cucumber testing.

One of our cucumber tests run fairly slow. In stead of guessing on where our application is spending time, I'd like to know programatically.

How do I trigger a cucumber test with a profiler???

What did not work:

  $ URL=/projects/by/114951412 #URL to slow rails page
  $ script/performance/profiler 'app.get "$URL"' 50

This does not work because 'app.get' only works in console and not available for profiler script

  $ EXPENSIVE_METHOD="Project.find('6300003243').aggregated_total_amount"
  $ script/performance/profiler "$EXPENSIVE_METHOD" 50

This gives a result but I have to guess that this method is the bottleneck

(I'm using cucumber 0.3.94, rails 2.3.2, ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9.6.0])

Answer 1

One more experiment is actually an answer to my question but did not give me but does not really give me a particularly useful result

$ PROJECT_DIR=`pwd`
$ which cucumber
/usr/local/bin/cucumber
$ ln -s `which cucumber` cukes #required for profiler to have local file in next step
$ ruby-prof cukes -- features/manager_overview.feature:36

This actually runs the single cucumber scenario on line 36, but the result is not particularly useful

Answer 2

Also try cucumber --format usage to get some stats about the slowest steps.

Answer 3

Using ruby-prof, you can start the profiler before the subject code and stop it again after. eg.:

require 'ruby-prof'
RubyProf.start
# code here
result = RubyProf.stop

# You can then output the trace in different ways.
# Simply print a overview to stdout
printer = RubyProf::FlatPrinter.new(result)
printer.print($stdout, :min_percent => 0.1)

# Save a callgrind trace
# You can load this up in kcachegrind or a compatible tool.
printer = RubyProf::CallTreePrinter.new(result)
File.open "callgrind.out.42", 'w' do |file|
  RubyProf::CallTreePrinter.new(result).print(file)
end