deamon
deamon

Reputation: 92437

Mocking objects without no-argument constructor in C# / .NET

Is it possible to create a mock from a class that doesn't provide a no-argument constructor and don't pass any arguments to the constructor? Maybe with creating IL dynamically?

The background is that I don't want to define interfaces only for testing. The workaround would be to provide a no-argument constructor for testing.

Upvotes: 48

Views: 32354

Answers (2)

Tejs
Tejs

Reputation: 41246

Sure thing. In this example i'll use Moq, a really awesome mocking library.

Example:

public class MyObject
{
     public MyObject(object A, object B, object C)
     {
          // Assign your dependencies to whatever
     }
}

Mock<MyObject> mockObject = new Mock<MyObject>();
Mock<MyObject> mockObject = new Mock<MyObject>(null, null, null); // Pass Nulls to specific constructor arguments, or 0 if int, etc

In many cases though, I assign Mock objects as the arguments so I can test the dependencies:

Mock<Something> x = new Mock<Something>();
MyObject mockObject = new MyObject(x.Object);

x.Setup(d => d.DoSomething()).Returns(new SomethingElse());

etc

Upvotes: 75

Darin Dimitrov
Darin Dimitrov

Reputation: 1038840

It is wrong to believe that you are providing interfaces only for testing. Interfaces are there to provide abstractions and weaken the coupling between the different layers of your code making them more reusable in different contexts.

This being said the answer will depend on the mocking framework you are using. For example with Rhino Mocks you could have:

public class Foo
{
    public Foo(string bar)
    { }

    public virtual int SomeMethod()
    {
        return 5;
    }
}

and then:

var fooMock = MockRepository.GeneratePartialMock<Foo>("abc");
fooMock.Expect(x => x.SomeMethod()).Return(10);

Upvotes: 2

Related Questions