moq

What problem does it solve?

Moq provides type-safe mocking for .NET unit tests, enabling you to isolate the system under test by replacing real collaborators with test doubles. This reduces flakiness and clarifies behavior verification across small and large codebases.

Core Features & Use Cases

• Type-safe mocking: Create Mock<T> instances to stand in for interfaces and classes under test.
• Interaction verification: Assert that specific methods were called, with expected arguments and call counts.
• Async support and callbacks: Use ReturnsAsync, Callback, and It.IsAny to model asynchronous behavior and capture inputs.
• Real-world scenarios: Test services, controllers, and workflows in Sorcha by isolating dependencies like repositories and external clients.

Quick Start

To begin using Moq, declare mocks in your test class, initialize Mock<T> dependencies in the constructor, and inject their .Object into the System Under Test. Then configure behavior with Setup and verify with Verify. For example:

• Initialize mocks: public class WalletManagerTests { private readonly Mock<ICryptoModule> _mockCryptoModule; private readonly Mock<IHashProvider> _mockHashProvider; public WalletManagerTests() { _mockCryptoModule = new Mock<ICryptoModule>(); _mockHashProvider = new Mock<IHashProvider>(); } }