Question

Can I use an Expression Tree as an argument constraint in a FakeIteasy CallTo assertion?

Given a method on an interface with the following signature:

interface IRepository<TEntity>
{
    TEntity Single(Expression<Func<TEntity, bool>> predicate);

Being called in code like so:

Flight flight = repository.Single(f => f.ID == id);

I have in mind a unit test doing something like this:

Expression<Func<Flight, bool>> myExpression = flight => flight.ID == 1;

A.CallTo(() => repository.Single(
                  A<Expression<Func<Flight, bool>>>.That.Matches(myExpression)))
                  .Returns(new Flight());

However this produces a warning: Try specifying type arguments explicitly.

I am currently having to use the Ignored property which is not ideal.

Answer 1

Thanks Patrik,

Examining the expression was exactly what I needed to do, i.e. parse the expression (f => f.ID == id) and execute the Right side of the == to get its runtime value.

In code this looks like this:

A.CallTo(() => flightRepository.Single(A<Expression<Func<Flight, bool>>>.That
                .Matches(exp => Expression.Lambda<Func<int>>(((BinaryExpression)exp.Body).Right).Compile().Invoke() == 1)))
                .Returns(new Flight());

However I can’t help thinking that there must be a more elegant way to achieve the same end. I’ll leave that for another day though.

Thanks again,
Michael McDowell