Ah, I can see why you're doing this now. It's because the method name would change inside the delegate. OK, this is one of the edge cases :wink:.

This gives me a nice idea for xbehave. In the 1.1 release, step overloads have been introduced which take an `IStepContext` parameter. We could introduce metadata to that object which supplied the name of the scenario to avoid you having to do this reflection stuff here. I've raised https://github.com/xbehave/xbehave.net/issues/146