Net4x.DapperLibrary.Mock 1.9.9.7

DapperLibrary.Mock

In-memory/mock provider integration for DapperLibrary. This project supplies a mock ADO.NET provider and a MockedDapperContext implementation useful for unit tests, integration tests and examples where a real database is not required.

Purpose

Provide a fast, deterministic, test-friendly mock provider that implements the same DapperContext surface without requiring an actual database engine. This enables unit tests to run quickly and independently of external resources.

Features

• MockedDapperContext � a DapperContext implementation backed by a mock provider.
• MockProviderFactory � a provider factory that delegates to a mock DbProviderFactory (MockFactory) and configures ParameterModel behavior.
• MockDatabaseModel, MockDatabaseModelTypes, MockDatabaseEnumTypes � type and model mappings that mirror common SQL Server behaviors for compatibility with DapperLibrary APIs.
• Adapter event forwarding for RowUpdating / RowUpdated on the mock data adapter used by the provider factory.

Key types

• MockedDapperContext

  • Derives from DapperContext and wires the MockProviderFactory along with configuration via DapperConfigurationManager scoped to the mock provider namespace.
  • Provides Use, UseOnce and Use(string, string) helpers like other provider-specific contexts to integrate with DapperContextFactory.
  • When contexts are created via the helpers, the database model is configured with SQL Server-style defaults (identity initializer and datetime formatting).

• MockProviderFactory

  • Inherits from ProviderFactoryBase and uses a runtime mock DbProviderFactory from the Mock.Data assembly.
  • Sets ParameterModel.ParameterPrefix = "@" and ParameterModel.AddIndex = true to emulate SQL Server-style parameter handling.
  • Installs PrepareCommandParameters to keep parameter binding consistent with other providers in DapperLibraries.

Usage

Create and use the mock context in tests:

using var context = new MockedDapperContext();

// use context.Operations / context.Schema / context.SaveDataTable etc.

Register the mock context creator for code that consumes DapperContextFactory:

MockedDapperContext.Use();
// or
MockedDapperContext.UseOnce();

Use a named connection if you need to emulate multiple connections:

MockedDapperContext.Use("Data Source=Mock;Provider=MockProvider");

Multi-targeting & compatibility

• The mock provider project targets legacy frameworks (net35/net40) in the repository to maximize compatibility with older test projects. The mock provider is intended for use in unit tests and should be referenced by test projects targeting compatible frameworks.
• Because the mock provider does not depend on external database drivers, it is useful across multiple target frameworks included in the solution.

Synchronous vs asynchronous behavior

• The mock provider implements the same synchronous and asynchronous method names as the real providers. Async variants may run synchronously under the hood depending on the mock implementation but maintain the same API contract which simplifies testing of async application code.
• Use the Async-suffixed methods in tests to verify async flows; the mock provider's Task-returning methods will behave predictably for assertions.

Notes and best practices

• The mock provider mirrors SQL Server-like behavior for identifier delimiters and parameter conventions to minimize surprises in tests that also target SQL Server.
• Use the mock provider for unit tests where DB I/O is not required; for integration tests prefer provider-specific integration helpers (like MockSqlServer or provider integrations) that exercise real database behavior.

For implementation details review MockProviderFactory, MockedDapperContext, and the DbContexts types in this project.