[ https://jira.codehaus.org/browse/JBEHAVE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298483#comment-298483 ]
Brian Repko commented on JBEHAVE-778: ------------------------------------- Mauro - agreed - the overhead of timing is small, so just doing it all the time and adding it to StepResult makes tons of sense. We could do that in the 3.6 branch as well (its backward compatible). Once we decide where to code this (4.x AND? 3.6), then I would request to close this issue (make it about timing). We may want to open up the issue of AOP steps as an enhancement if it doesn't already exist. I know that it was asked on the user list (Christian Zulehner) a while back but I'm not sure that we have it captured as an enhancement. The issue is that the JBehave framework doesn't recognize those steps classes as the AOP wipes out the JBehave annotations and we talked about an unwrap method on some interface to get to the actual class. > Capture the execution time of steps annotated by @Profiled > ----------------------------------------------------------- > > Key: JBEHAVE-778 > URL: https://jira.codehaus.org/browse/JBEHAVE-778 > Project: JBehave > Issue Type: Story > Components: Core > Reporter: prem > Assignee: Mauro Talevi > Fix For: 4.0 > > > Create an annotation @Profiled to capture the execution time of a step: > @Given("I log into mail account as user <username> with password <password>") > @Profiled > public void login(){ > .... > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email