使用 TestScheduler 对 Akavache 的缓存行为进行单元测试

本文关键字:单元测试 缓存 TestScheduler Akavache 使用 | 更新日期: 2023-09-27 18:33:47

所以我正在尝试在使用Akavache的应用程序中测试缓存行为。我的测试如下所示:

using Akavache;
using Microsoft.Reactive.Testing;
using Moq;
using NUnit.Framework;
using ReactiveUI.Testing;
using System;
using System.Threading.Tasks;
[TestFixture]
public class CacheFixture
{
    [Test]
    public async Task CachingTest()
    {
        var scheduler = new TestScheduler();
        // replacing the TestScheduler with the scheduler below works
        // var scheduler = CurrentThreadScheduler.Instance;
        var cache = new InMemoryBlobCache(scheduler);
        var someApi = new Mock<ISomeApi>();
        someApi.Setup(s => s.GetSomeStrings())
            .Returns(Task.FromResult("helloworld")).Verifiable();
        var apiWrapper = new SomeApiWrapper(someApi.Object, cache,
            TimeSpan.FromSeconds(10));
        var string1 = await apiWrapper.GetSomeStrings();
        someApi.Verify(s => s.GetSomeStrings(), Times.Once());
        StringAssert.AreEqualIgnoringCase("helloworld", string1);
        scheduler.AdvanceToMs(5000);
        // without the TestScheduler, I'd have to 'wait' here
        // await Task.Delay(5000);
        var string2 = await apiWrapper.GetSomeStrings();
        someApi.Verify(s => s.GetSomeStrings(), Times.Once());
        StringAssert.AreEqualIgnoringCase("helloworld", string2);
    }
}

SomeApiWrapper使用一个内部 api(用 new Mock<ISomeApi>() 模拟),为了简单起见,它只返回一个字符串。现在的问题是第二个字符串永远不会返回。处理缓存的 SomeApiWrapper 类如下所示:

using Akavache;
using System;
using System.Reactive.Linq;
using System.Threading.Tasks;
public class SomeApiWrapper
{
    private IBlobCache Cache;
    private ISomeApi Api;
    private TimeSpan Timeout;
    public SomeApiWrapper(ISomeApi api, IBlobCache cache, TimeSpan cacheTimeout)
    {
        Cache = cache;
        Api = api;
        Timeout = cacheTimeout;
    }
    public async Task<string> GetSomeStrings()
    {
        var key = "somestrings";
        var cachedStrings = Cache.GetOrFetchObject(key, DoGetStrings,
            Cache.Scheduler.Now.Add(Timeout));
        // this is the last step, after this it just keeps running
        // but never returns - but only for the 2nd call
        return await cachedStrings.FirstOrDefaultAsync();
    }
    private async Task<string> DoGetStrings()
    {
        return await Api.GetSomeStrings();
    }
}

调试只会将我引向return await cachedStrings.FirstOrDefaultAsync();行 - 之后它永远不会完成。

当我用标准(CurrentThreadScheduler.Instance)替换TestScheduler,用await Task.Delay(5000)替换scheduler.AdvanceToMs(5000)时,一切都按预期工作,但我不希望单元测试运行几秒钟。

类似的测试,其中TestScheduler提前超过缓存超时也会成功。只是这种情况,缓存条目不应在两个方法调用之间过期。

我在使用TestScheduler的方式上做错了什么吗?

使用 TestScheduler 对 Akavache 的缓存行为进行单元测试

Task范式和IObservable范式之间跳动时,这是一个相当常见的问题。在测试中继续前进之前试图等待会进一步加剧这种情况。

关键问题是你在这里阻止*

return await cachedStrings.FirstOrDefaultAsync();

我说阻塞是指代码不能继续处理,直到这个语句产生。

在第一次运行时,缓存找不到密钥,因此它会执行您的DoGetStrings。该问题在第二次运行时出现,其中填充了缓存。这次(我猜)缓存数据的获取是预定的。您需要调用请求,观察顺序,然后泵送调度程序。

更正后的代码在这里(但需要一些 API 更改)

[TestFixture]
public class CacheFixture
{
    [Test]
    public async Task CachingTest()
    {
        var testScheduler = new TestScheduler();
        var cache = new InMemoryBlobCache(testScheduler);
        var cacheTimeout = TimeSpan.FromSeconds(10);
        var someApi = new Mock<ISomeApi>();
        someApi.Setup(s => s.GetSomeStrings())
            .Returns(Task.FromResult("helloworld")).Verifiable();
        var apiWrapper = new SomeApiWrapper(someApi.Object, cache, cacheTimeout);
        var string1 = await apiWrapper.GetSomeStrings();
        someApi.Verify(s => s.GetSomeStrings(), Times.Once());
        StringAssert.AreEqualIgnoringCase("helloworld", string1);
        testScheduler.AdvanceToMs(5000);
        var observer = testScheduler.CreateObserver<string>();
        apiWrapper.GetSomeStrings().Subscribe(observer);
        testScheduler.AdvanceByMs(cacheTimeout.TotalMilliseconds);
        someApi.Verify(s => s.GetSomeStrings(), Times.Once());

        StringAssert.AreEqualIgnoringCase("helloworld", observer.Messages[0].Value.Value);
    }
}
public interface ISomeApi
{
    Task<string> GetSomeStrings();
}
public class SomeApiWrapper
{
    private IBlobCache Cache;
    private ISomeApi Api;
    private TimeSpan Timeout;
    public SomeApiWrapper(ISomeApi api, IBlobCache cache, TimeSpan cacheTimeout)
    {
        Cache = cache;
        Api = api;
        Timeout = cacheTimeout;
    }
    public IObservable<string> GetSomeStrings()
    {
        var key = "somestrings";
        var cachedStrings = Cache.GetOrFetchObject(key, DoGetStrings,
            Cache.Scheduler.Now.Add(Timeout));
        //Return an observerable here instead of "blocking" with a task. -LC
        return cachedStrings.Take(1);
    }
    private async Task<string> DoGetStrings()
    {
        return await Api.GetSomeStrings();
    }
}

此代码为绿色,运行亚秒级。