Create a spy of Func<> and make it return a specific value for testing about nsubstitute

[GeraldLx]

Version 2 works for me without RedundantArgumentMatcherException and is the right syntax.

Personally I would ask if it is really a good thing to use a mocking framework for this test?
Why not just write the test without it?

E.g.:

  [TestMethod]
  public void TestIt()
  {
    var it = new DoIt();

    int? value1 = null;
    int? value2 = null;


    var actual = it.Execute((x, y) =>
    {
      value1 = x;
      value2 = y;

      return true;
    });

    actual.Should().BeTrue();
    value1.Should().Be(1);
    value2.Should().Be(2);
  }

Not as fancy as the NSubstitute version but way easier to understand.

[hicks86]

Thank you, so the 2nd way is probably what I need to go for, maybe I need an update.

But yeah you make a good point, I can do all that funky mocking manually and at least I have control and know what it is doing.
Damn I fell back into the "mock all the things" trap.

Cheers

[304NotModified]

I think the question has been answered and therefore I will close this one.

Please let us know if you need further information or would like us to take another look at this