Make Advice consume IMethodAdviceContext instead of MethoadAdviceContext

I have an attribute that consumes IMethodAdvise which I want to test. I’ve tried testing it’s advise method and stepped into a problem:

1. MethodAdviceContext has not parallel interface to mock by.
2. some of MethodAdviceContext's Constructor parameters are Internal (and also have not interface) and therefore I cannot instantiate them (and therefore, no testing for me 😦 )

[shirbr510]

Kinda forgot to try it… tried it now and works like charm 😃

again, thank you for listening and making it work 😃

[shirbr510]

True. I can pass down parameters to anything rather Easely except one case: context.Proceed()

wrapping it is possible but it will look rather close to Microsoft’s HttpContextWrapper solution for the sealed HttpContext (if you know what I’m speaking of), which I personally prefer to avoid

On Wed, Jul 6, 2016 at 6:34 PM, Pascal Craponne [e-mail] wrote:

From the methods above, which ones do you intend to test? If you test only the OnEnter, OnExit and OnException you can simply pass the required MethodAdviceContext properties instead of passing the whole instance. Same thing (a little bit heavier though) if you test the LogMethod, no?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ArxOne/MrAdvice/issues/63#issuecomment-230809885, or mute the thread https://github.com/notifications/unsubscribe/AGJYEuB_SVzgFwCMmvwIkcMyaLhX7pXZks5qS8sKgaJpZM4JFD6I .