Feature request: Then().Returns...()

[drauch]

Feature request: Then().Returns...()

[blairconrad]

Hi, @drauch. I may be missing a subtlety. Can you show some code? Ideally what you have to do now to workaround the lack, and an envisioned improvement? Because as I read your description upstairs, I'm not sure how what you're asking for is different than Specifying different behaviors for successive calls:

public interface IDoSomething
{
    int DoSomething(int input);
}

public void Test1()
{
    var fake = A.Fake<IDoSomething>();
    A.CallTo(() => fake.DoSomething(A<int>._))
        .ReturnsLazily((int i) => i * 2).Once()
        .Then
        .ReturnsLazily((int i) => i * 2).Once();

    var doubleOne = fake.DoSomething(1);
    var doubleThree = fake.DoSomething(3);

    doubleOne.Should().Be(2);
    doubleThree.Should().Be(6);
}

[drauch]

I need it in two different locations:

void Arrange1 ()
{
    A.CallTo(() => fake.Foo()).Returns(1).Once();
}

void Arrange2 ()
{
    A.CallTo(() => fake.Foo()).Then.Returns(2).Once();
}

Best regards,
D.R.

[blairconrad]

This seems kind of niche, to be honest. It looks like you have access to fake from some shared location (perhaps it's an instance variable). Have you considered retaining the result of A.CallTo(() => fake.Foo()).Returns(1).Once()?

private IDoSomething? fake;
private IThenConfiguration<IReturnValueConfiguration<int>>? ongoingFakeConfiguration;

public interface IDoSomething
{
    int Foo();
}

void Arrange1()
{
    ongoingFakeConfiguration = A.CallTo(() => fake!.Foo()).Returns(1).Once();
}

void Arrange2()
{
    ongoingFakeConfiguration = ongoingFakeConfiguration!.Then.Returns(2).Once();
}

[Fact]
public void Test1()
{
    fake = A.Fake<IDoSomething>();

    Arrange1();
    Arrange2();

    var result1 = fake.Foo();
    var result2 = fake.Foo();

    result1.Should().Be(1);
    result2.Should().Be(2);
}

It doesn't seem any worse to me than the existing temporal coupling.

[drauch]

Okay, that's also a workaround I guess.

[blairconrad]

This may be a disappointment, but we've decided not to implement this change. While it may be useful for some, there are abundant alternate flows.