You could do this yourself crudely by adding "eval" steps to the OnProcedureEnter and OnProcedureExit events and then picking up the values and doing something with them. Or even more crudely, you could just add eval steps at the start and end of interesting procedures. The [info] and [clock] commands gives you access to information you'll probably want.
One suggestion I'd gotten on this was to hook into com.fnfr.open.automation.enginemonitor and tack listeners onto onPreparingStep(IStep, IExecutionDirective) and procedure steps.
Haven't tried it yet as I've been busy with other things, but seems like a nice way to avoid users embedding things in their script.
That is correct. Engine Monitor SDK can be used to generate any form of test report you want because you have access to complete information resulting from executing a step.
I am not sure how effective it is to use onPreparingStep since IStep ( or our executable step ) does not have notion of a being a procedure step, it is a just a step and one can not use step action being "call" as we now have quick call feature..
What Kingston suggested seems to be a better way to go...
