菜单
Creates mock objects and configures test dependencies with Moq. Use when: writing unit tests that need to isolate dependencies, verify method calls, or simulate service behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Builds REST APIs, SignalR hubs, and ASP.NET Core Web API applications. Use when: Creating controllers, configuring middleware, setting up dependency injection, implementing background services, or working with the API layer.
Develops Blazor WebAssembly single-page applications with component-based UI. Use when: Creating/modifying .razor components, managing component state, handling SignalR subscriptions, or working with MudBlazor UI components.
Writes C# code following VanDaemon conventions and clean architecture patterns Use when: Creating services, entities, controllers, or plugins in the VanDaemon codebase
Configures containerization with Docker and Docker Compose for VanDaemon. Use when: building containers, configuring docker-compose, deploying to Docker environments, troubleshooting container networking, or setting up multi-container applications.
Configures .NET 10 projects, builds, and manages C# runtime. Use when: building/running the solution, adding projects, managing NuGet packages, configuring Docker containers, or troubleshooting build issues.
Writes fluent, readable test assertions and validations using FluentAssertions library. Use when: Writing unit tests, validating service responses, asserting domain entity states, testing collections and async operations.
| name | moq |
| description | Creates mock objects and configures test dependencies with Moq. Use when: writing unit tests that need to isolate dependencies, verify method calls, or simulate service behavior. |
| allowed-tools | Read, Edit, Write, Glob, Grep, Bash |
Moq is the mocking framework used throughout VanDaemon for unit testing. All services are registered as singletons and depend on interfaces, making them ideal candidates for mocking. Tests use Mock<T> to create test doubles, Setup() to configure behavior, and Verify() to assert interactions.
// Mock a service interface
var mockTankService = new Mock<ITankService>();
mockTankService
.Setup(x => x.GetAllTanksAsync(It.IsAny<CancellationToken>()))
.ReturnsAsync(new List<Tank> { new Tank { Id = Guid.NewGuid(), Name = "Fresh Water" } });
var controller = new TanksController(mockTankService.Object);
var mockControlService = new Mock<IControlService>();
mockControlService
.Setup(x => x.SetControlStateAsync(
It.Is<Guid>(id => id != Guid.Empty),
It.IsAny<object>(),
It.IsAny<CancellationToken>()))
.ReturnsAsync(true);
| Concept | Usage | Example |
|---|---|---|
Mock<T> | Create mock instance | new Mock<ITankService>() |
.Object | Get mocked instance | mock.Object |
Setup() | Configure method behavior | .Setup(x => x.Method()) |
Returns() | Sync return value | .Returns(value) |
ReturnsAsync() | Async return value | .ReturnsAsync(value) |
It.IsAny<T>() | Match any argument | It.IsAny<CancellationToken>() |
It.Is<T>() | Match with predicate | It.Is<Guid>(g => g != Guid.Empty) |
Verify() | Assert method called | .Verify(x => x.Method(), Times.Once) |
var mockLogger = new Mock<ILogger<TankService>>();
var service = new TankService(mockLogger.Object, mockFileStore.Object);
// Verify logging occurred (Moq can't verify extension methods directly)
// Use LoggerFactory or just trust the implementation
var mockFileStore = new Mock<IJsonFileStore>();
mockFileStore
.Setup(x => x.LoadAsync<List<Tank>>("tanks.json", It.IsAny<CancellationToken>()))
.ReturnsAsync(testTanks);
var mockHubContext = new Mock<IHubContext<TelemetryHub>>();
var mockClients = new Mock<IHubClients>();
var mockGroup = new Mock<IClientProxy>();
mockHubContext.Setup(x => x.Clients).Returns(mockClients.Object);
mockClients.Setup(x => x.Group("tanks")).Returns(mockGroup.Object);