2

I seen this post but I am sort of confused by it.

How can I mock Elmah's ErrorSignal routine?

I am looking at option 2

Create a wrapper class around the call to Raise and just mock out the wrapper class.

public class ErrorSignaler {

public virtual void SignalFromCurrentContext(Exception e) {
    if (HttpContext.Current != null)
        Elmah.ErrorSignal.FromCurrentContext().Raise(e);
}

}

I am kinda confused though by the fact that this does not seem to implement an interface and I am not really sure why it seems to be in place for some sort of inheritance.

Thanks

Community
  • 1
  • 1
chobo2
  • 83,322
  • 195
  • 530
  • 832

1 Answers1

2

The idea here is that you would use the ErrorSignaler class in your code to signal an error instead of invoking Elmah directly. When running your code in unit tests, because HttpContext.Current is null, the Elmah component won't be used, and there won't be any null reference exceptions.

You could also create an ErrorSignaler interface:

public interface IErrorSignaler
{
    void SignalFromCurrentContext(Exception e);
}

That way the implementation used to implement IErrorSignaler can be mocked in the unit tests if required.

Nader Shirazie
  • 10,736
  • 2
  • 37
  • 43
  • Ya that's what I ended up doing then I mocked it. I just was wondering the guy had "Virtual" – chobo2 Sep 07 '09 at 18:24
  • That would allow him to subclass the ErrorSignaler to add even more behaviour to the `Signal` method. That flexibility could be useful in some situtations. – Nader Shirazie Sep 07 '09 at 18:30