我可以在Rhino-Mocks 3.6中使用AAA语法测试方法调用顺序吗？

Question

在 Rhino-mocks 3.6 中，是否可以使用 AAA 语法测试以下示例：如果 Method1 调用第一个，然后 Method2 调用之后，然后调用 Method3 ？

// Assert
var mock = MockRepository.GenerateMock<ISomeService>();

// Act
myObject.Service = mock;

// How should I change this part to ensure that Rhino Mocks check the call order as well?
mock.AssertWasCalled(m=>m.Method1());
mock.AssertWasCalled(m=>m.Method2());
mock.AssertWasCalled(m=>m.Method3());

Answer 1

这是一种方法......

mock.AssertWasCalled(m=>m.Method1(), options => options.WhenCalled(w => mockService.AssertWasNotCalled(x=>x.Method2())));
mock.AssertWasCalled(m=>m.Method2(), options => options.WhenCalled(w => mockService.AssertWasNotCalled(x=>x.Method3())));
mock.AssertWasCalled(m=>m.Method3());

Answer 2

你可以，但你真的不应该。您应该专注于测试外部可观察的行为，而不是实现。

方法调用顺序可以更改，而不会影响与 API 客户端的契约。在这种情况下，您的测试将会失败，即使它不应该失败。

简而言之，测试实施会导致测试变得脆弱。脆性测试导致放弃测试。你不想去那里。

希望这有帮助。

Answer 3

以下是如何做得很好。

var mocks = new MockRepository();
var fooMock = mocks.DynamicMock<IFoo>();
using (mocks.Ordered())
{
    fooMock.Expect(x => x.Method1());
    fooMock.Expect(x => x.Method2());
}
fooMock.Replay();

var bar = new Bar(fooMock);
bar.DoWork();

fooMock.VerifyAllExpectations();

从这篇博客文章中找到了答案：使用 Rhino Mocks 3.5 验证方法执行的顺序 作者：Philip Japikse

Answer 4

以下是如何通过在每个方法调用中构建断言来实现这一点。

// Arrange - Build the necessary assertions into the stubbed method invocations.
var mock = MockRepository.GenerateMock<ISomeService>();
mock.Stub(m => m.Method1()).WhenCalled(inv => mock.AssertWasNotCalled(m => m.Method2()));
mock.Stub(m => m.Method2()).WhenCalled(inv => mock.AssertWasNotCalled(m => m.Method3()));

// Act
myObject.Service = mock;

// Assert - Ensure each expected method was called.
mock.AssertWasCalled(m => m.Method1());
mock.AssertWasCalled(m => m.Method2());
mock.AssertWasCalled(m => m.Method3());

由于这是通过在中间运行断言来混合正常的排列-行为-断言模式，因此我喜欢为这些实例包含非常具体的错误消息，以便更轻松地识别测试失败。

mock.Stub(m => m.Method1()).WhenCalled(inv =>
    mock.AssertWasNotCalled(m => m.Method2(), opt =>
        opt.Message("Method2 cannot be called before Method1.")));

您还可以通过在执行步骤期间将每次调用的结果保存在变量中，然后在断言步骤期间检查变量状态来获得类似的结果。这更好地保留了排列-行为-断言模式的划分，但需要编写和维护更多的管道代码。

// Arrange - Build the necessary state variables into the stubbed method invocations.
bool wasMethod1Called;
bool wasMethod2Called;
bool wasMethod2CalledBeforeMethod1;
bool wasMethod3CalledBeforeMethod2;

var mock = MockRepository.GenerateMock<ISomeService>();
mock.Stub(m => m.Method1()).WhenCalled(inv =>
{
    wasMethod1Called = true;
});
mock.Stub(m => m.Method2()).WhenCalled(inv =>
{
    wasMethod2Called = true;
    wasMethod2CalledBeforeMethod1 = !wasMethod1Called;
});
mock.Stub(m => m.Method3()).WhenCalled(inv =>
{
    wasMethod3CalledBeforeMethod2 = !wasMethod2Called;
});

// Act
myObject.Service = mock;

// Assert - Ensure each expected method was called, and that they were called in the right order.
mock.AssertWasCalled(m => m.Method1());
mock.AssertWasCalled(m => m.Method2());
mock.AssertWasCalled(m => m.Method3());
Assert.That(wasMethod2CalledBeforeMethod1, Is.False, "Method2 cannot be called before Method1.");
Assert.That(wasMethod3CalledBeforeMethod2, Is.False, "Method3 cannot be called before Method2.");

Answer 5

@craastad 指定的 mocks.Ordered() 语法是正确的方法，但我无法让它在 RhinoMocks 3.5 中工作 - 相反，我必须调整它以在没有 @craastad 的解决方案使用的 MockRepository 实例的情况下工作调用 Ordered() ：

var fooMock = MockRepository.GenerateMock<IFoo>();
using (fooMock.GetMockRepository().Ordered())
{
    fooMock.Expect(x => x.Method1());
    fooMock.Expect(x => x.Method2());
}

var bar = new Bar(fooMock);
bar.DoWork();

fooMock.VerifyAllExpectations();

如果你这样做，似乎也没有必要调用 fooMock.Replay() 。