Azure函数单元测试：Moq模拟Blob仓储Add方法抛异常失败求助

Let's break down why your Add method exception test is failing while others work. Based on your code, here are the most likely issues and fixes:

1. Moq Setup Parameter Mismatch #

This is the most common culprit when a specific mock test fails. Let's look at your setup:

iblobStorageRepositoryMoq
    .Setup(mock => mock.Add(logger, correlationId, body, userObject))
    .ThrowsAsync(new Exception("Function Add threw an exception"));

But in your SettingsStore.AddUserSettingsAsync method, you're probably serializing the userSettingsObject to a string before passing it to Add—right? The problem is:

• The body variable in your test is read from a file (File.ReadAllText("TestData/userSettings.json"))
• The serialized string generated by JsonConvert.SerializeObject(userSettingsObject) in production code might not match exactly (e.g., different indentation, casing, or null handling settings in Json.NET)

Moq uses strict parameter matching by default, so even a tiny difference in the string will cause the setup to not trigger.

Fix: #

Either:

• Use flexible parameter matching with It.IsAny<T> to bypass strict checks (great for debugging):

  iblobStorageRepositoryMoq
      .Setup(mock => mock.Add(It.IsAny<ILogger>(), It.IsAny<string>(), It.IsAny<string>(), It.IsAny<string>()))
      .ThrowsAsync(new Exception("Function Add threw an exception"));
  

• Or serialize the test object the same way your production code does, then use that string in the setup:

  // Match the serialization logic from SettingsStore
  string serializedSettings = JsonConvert.SerializeObject(userSettingsObject);
  iblobStorageRepositoryMoq
      .Setup(mock => mock.Add(logger, correlationId, serializedSettings, userObject))
      .ThrowsAsync(new Exception("Function Add threw an exception"));
  

2. Exception Type Mismatch #

Your test expects an InvalidOperationException:

Exception exception = await Assert.ThrowsAsync<InvalidOperationException>(...);

But your Moq setup throws a generic Exception. Ask yourself: Does SettingsStore.AddUserSettingsAsync wrap the blob repository's exception into an InvalidOperationException?

Scenarios: #

• If your SettingsStore doesn't wrap exceptions: The test will fail because it's expecting an InvalidOperationException but gets a plain Exception. Fix the test to assert the correct type:

  Exception exception = await Assert.ThrowsAsync<Exception>(async () => await settingsStore.AddUserSettingsAsync(...));
  

• If your SettingsStore does wrap exceptions: It probably preserves the inner exception, so your Assert.Null(exception.InnerException) will fail. Update the assertion to check the inner exception instead:

  Assert.Equal("Function Add threw an exception", exception.InnerException.Message);
  

3. Logger Instance Mismatch #

If the logger instance you pass to settingsStore.AddUserSettingsAsync isn't the exact same one used in your Moq setup, Moq will ignore the setup (since it matches by reference).

Fix: #

Use It.IsAny<ILogger>() to match any logger instance in your setup:

iblobStorageRepositoryMoq
    .Setup(mock => mock.Add(It.IsAny<ILogger>(), correlationId, It.IsAny<string>(), userObject))
    .ThrowsAsync(new Exception("Function Add threw an exception"));

4. Verify the Mock Was Actually Called #

To confirm your setup is being hit, add a verification step at the end of your test:

iblobStorageRepositoryMoq.Verify(
    mock => mock.Add(It.IsAny<ILogger>(), correlationId, It.IsAny<string>(), userObject),
    Times.Once,
    "Blob storage Add method was not called as expected"
);

If this verification fails, it means your SettingsStore isn't calling the blob repository's Add method at all—check the production code logic for conditional checks that might skip the call.

内容的提问来源于stack exchange，提问作者Bjarne B. Dollerup