Mocking abstract classes

Hi Paulo.

Nice one.
the easiest way I see to test this is:

public class Class1 : MyClass
{
  protected override void MyMethod()
  { }
}

[Test]
[VerifyMocks]
public void test()
{
  Mock mock = MockManager.Mock<Class1>(Constructor.NotMocked);
  mock.ExpectCall("MyMethod");

  Class1 target = new Class1();
}

That's how I did it. But I was hoping for something more "Natural"

Its an egg and chicken problem.
In order to set expectations you need to create the MockObject.
When you create the MockObject the constructor is invoked/mocked.

Anyway Ill add this to our future list and see if we can give a good solution for this.

We might get into a little of a purist argument on this one, but I might actually just stub out a derived class and skip mocking altogether. Yeah, a little longer and a little messier, but it doesn't require any special understanding of what's going on for later test maintainers.

public abstract MyClass 
{ 
  public MyClass() 
  { 
    MyMethod(); 
  } 

  protected abstract MyMethod(); 
}

[TestFixture]
publc UnitTests
{
  [Test]
  public void MyMethodGetsCalled()
  {
    DerivedClass testObject = new DerivedClass();
    Assert.IsTrue(testObject.MyMethodWasCalled);
  }
  
  public DerivedClass : MyClass
  {
    public bool MyMethodWasCalled = false;
    
    protected override MyMethod()
    {
      this.MyMethodWasCalled = true;
    }
  }
}

It works, but it's not fun. :)

Let's get purist here. Isn't that a mock. You can check your expectations in the end.