MSTest新手遇TaskAwaiter异常，求技术支持（附测试代码）

Hey there! I totally get being stuck on this vague-looking error when you're new to MSTest—this exception can feel like a dead end at first, but let's break down what's actually going on and how to fix it.

First off: this TaskAwaiter exception is just a wrapper. It's MSTest's way of telling you an asynchronous task in your test failed, but the real root cause is hidden in the exception's InnerException property. That's where you need to look first.

Step 1: Uncover the Real Error #

• When debugging, hover over the exception object and expand the InnerException field—this will show you the actual message and stack trace of what went wrong (e.g., a null reference, an unconfigured mock, or a missing dependency).
• If you're not debugging, check the full test failure details in the MSTest Test Explorer—most of the time it will display the inner exception there too.

Step 2: Check Common Async Test Pitfalls #

Based on your code snippet, here are the most likely issues to investigate:

1. Incorrect Mock Setup for Async Methods

You're using Mock<IStorageService>—if the methods you're mocking are asynchronous (return Task or Task<T>), you need to use ReturnsAsync instead of plain Returns. Using Returns will return a synchronous value that doesn't properly wrap into a completed Task, which triggers this exception.

Wrong:

mockStorage.Setup(s => s.GetYourAsyncMethod()).Returns(new List<Solution>());

Right:

mockStorage.Setup(s => s.GetYourAsyncMethod()).ReturnsAsync(new List<Solution>());

2. Missing await on Async Calls

Double-check that every asynchronous method in your test (or the code under test) is properly awaited. Forgetting await can leave Tasks incomplete before the test finishes, or let unhandled exceptions bubble up through this TaskAwaiter wrapper.

3. Test Context/Authentication Issues

You set AuthenticatedUsername = "xxx@yyy.com"—make sure this value is actually being picked up by the code under test. If the service you're testing expects this username in a specific context (like a claims principal or service property), verify it's properly injected or set before executing test logic.

4. Accidentally Using the Wrong Mock Instance

I noticed you created both storageService and mockStorage in your test—are you accidentally passing the wrong mock instance to the service under test? That could lead to null references or unconfigured methods being called, which would throw an exception in the async flow.

Quick Debugging Trick #

If you're still stuck, wrap your test logic in a try-catch block to explicitly log the inner exception:

[TestMethod]
public async Task GetReturnsAllSolutionsForAdminUser()
{
    try
    {
        var mockStorage = new Mock<IStorageService>();
        var mockGeneralServices = new Mock<IGeneralServices>();
        AuthenticatedUsername = "xxx@yyy.com";

        // Configure your mocks correctly
        mockStorage.Setup(s => s.GetSolutionsAsync()).ReturnsAsync(new List<Solution>());

        // Initialize your service under test with the mocks
        var service = new YourService(mockStorage.Object, mockGeneralServices.Object);

        // Execute the test
        var result = await service.GetReturnsAllSolutionsForAdminUser();

        // Add your assertions
        Assert.IsNotNull(result);
    }
    catch (Exception ex)
    {
        // Log the root cause details
        Console.WriteLine($"Root cause: {ex.InnerException?.Message}");
        Console.WriteLine($"Stack trace: {ex.InnerException?.StackTrace}");
        throw; // Re-throw to let the test fail normally
    }
}

Once you find the inner exception, fixing the actual problem will be straightforward.

内容的提问来源于stack exchange，提问作者Debo