I'm not trying to say that as soon as a good project is left behind from its creator, it means that the users should go away from it, as Ayende says as for this goal, it's done, in my opinion that latest release of RhinoMocks could be useful for the next 5 years. The new owner seems to have good ideas for the next versions of RhinoMocks. However, the community and life in general is moving at a different speed and sometimes we have to find a substitute even if we like the current one item.
According to the community, after some research on the internet and based on several well-documented stackoverflow answers, Moq is the best alternative, it's based on Linq and Expressions and it can be used in very simple ways which is good for the increasing amount of developers who are starting to use TDD or just trying to automate some tests.
Let's refresh the simple repository interfaces to be mocked:
public interface IIdentityKey<Tkey>
{
TKey Id { get; set; }
}
public interface IRepository<Tkey,TEntity> where TEntity : IIdentityKey<Tkey>
{
IQueryable<TEntity> All();
TEntity FindBy(TKey id);
TEntity Add(TEntity entity);
void Update(TEntity entity);
void Delete(TEntity entity);
}
In our controller we use this interface as it will be injected using any IoC such as Ninject, but important here is that the controller doesn't know or even cares the actual implementation of this repository, this is a fragment of our controller:
public class PersonController : ApiController
{
private readonly IRepository<long, Person> _repository;
public PersonController(IRepository<long, Person> repository)
{
_repository = repository;
}
// GET api/person
public IEnumerable<Person> Get()
{
return _repository.All().ToArray();
}
// the rest of the code removed for brevity ...
}
We need to create the 5 methods previously mentioned in the interface in a way that they make the operations on a list with initial data, such as this:
private List<Person> _fakedata = new List<Person> {
new Person { Id = 1, Name = "Person1", Email = "person1@nomail.com" },
new Person { Id = 2, Name = "Person2", Email = "person2@nomail.com" },
// ( ... )
new Person { Id = 8, Name = "Person8", Email = "person8@nomail.com" }
};
Let's start with the actual mock creation and set up now using Moqprivate IRepository<TK, TE> CreateRepository<TK, TE>(List<TE> data)
where TE : class, IIdentityKey<TK>
{
var mock = new Mock<IRepository<TK, TE>>();
// all the mocking setup goes here ...
return mock.Object;
}
The actual mock procedure is made through the combination of Setup(...).Returns(...) and Setup(...).Callback(...) for methods that return something and void respectively. The All() method is done this way.// setup All method mock.Setup(x => x.All()).Returns(data.AsQueryable());The Returns() method accepts an object of the same type as the return type in Setup() argument or a Func with return type the same as declared in Setup, so it matches the signature at runtime. In that example it's just return the raw list previously declared.
// setup Add method
mock.Setup(x => x.Add(It.IsAny<TE>()))
.Returns(new Func<TE, TE>(x => {
dynamic lastId = data.Last().Id;
dynamic nextId = lastId + 1;
x.Id = nextId;
data.Add(x);
return data.Last();
}));
The Add() method is implemented using a bit more complex behaviour in order to simulate the auto incremental in database helped by dynamics for not to force a concrete type as in C# there's no generic constraint for only numeric types.// setup Update method
mock.Setup(x => x.Update(It.IsAny<TE>()))
.Callback(new Action<TE>(x =>
{
var i = data.FindIndex(q => q.Id.Equals(x.Id));
data[i] = x;
}));
// setup FindBy (id)
mock.Setup(x => x.FindBy(It.IsAny<TK>()))
.Returns(new Func<TK, TE>(
x => data.Find(q => q.Id.Equals(x))
));
// setup Delete
mock.Setup(x => x.Delete(It.IsAny<TE>()))
.Callback(new Action<TE>(x => {
var i = data.FindIndex(q => q.Id.Equals(x.Id));
data.RemoveAt(i);
}
));
Following the same idea, we've got the remaining methods from the interface implementation. Earlier I mentioned a generic method which accepts two arguments: TK and TE related to type of key and of entity, now it will be called by another method for this specific controller.
private PersonController CreateController()
{
IRepository<long, Person> repo = CreateRepository<long, Person>(_fakedata);
PersonController target = new PersonController(repo);
return target;
}
Finally, the test should look like this fragment:
[TestMethod]
public void Get()
{
// Arrange
PersonController controller = CreateController();
// Act
IEnumerable<Person> result = controller.Get();
// Assert
Assert.IsNotNull(result);
Assert.AreEqual(8, result.Count());
Assert.AreEqual("Person1", result.ElementAt(0).Name);
Assert.AreEqual("Person8", result.ElementAt(7).Name);
}
[TestMethod]
public void GetById()
{
// Arrange
PersonController controller = CreateController();
// Act
Person result = controller.Get(5);
// Assert
Assert.AreEqual("Person5", result.Name);
}
We invoke the CreateController method on each test so the logic previously described is encapsulated and then a new instance of the controller with the mocked repository inside. The sample code can be downloaded here.
