unit testing - Hard-Coded Mock Objects vs Mocking Framework

Question

I'm curious as to what method people like to use for mocking and why. The two methods that I know of are using hard coded mock objects and a mocking framework. To demonstrate, I'll outline an example using C#.

Suppose we have an IEmployeeRepository interface with a method called GetEmployeeById.

public interface IEmployeeRepository
{
    Employee GetEmployeeById(long id);
}

We can easily create a mock of this:

public class MockEmployeeRepository : IEmployeeRepository
{
    public Employee GetEmployeeById(long id)
    {
        Employee employee = new Employee();
        employee.FirstName = "First";
        employee.LastName = "Last";
        ...
        return employee;
    }
}

Then, in our tests we can explicitly tell our services to use the MockEmployeeRepository, either using a setter or dependency injection. I'm new to mocking frameworks so I'm curious as to why we use them, if we can just do the above?

Answer 1

That's not a Mock, it's a Stub. For stubbing, your example is perfectly acceptable.

From Martin Fowler:

Mocks are what we are talking about here: objects pre-programmed with expectations which form a specification of the calls they are expected to receive.

When you're mocking something, you usually call a "Verify" method.

Look at this for the diff between Mocks and Stubs http://martinfowler.com/articles/mocksArentStubs.html