-
-
Notifications
You must be signed in to change notification settings - Fork 1
MiniProfiler Integration
LAP-CHRIS\chris edited this page Mar 10, 2026
·
1 revision
Language: English | Português (Brasil)
The current packaged MiniProfiler adoption path is centered on DbSqlLikeMem.MySql.MiniProfiler, which lets MySQL-oriented test flows compose profiling with the same mock connection approach used in the core library.
- Your test setup already uses MiniProfiler
- You want profiling around a MySQL mock connection
- You also want to compose DbConnection Interception for recording, logging, or fault injection
var profiled = new ProfiledDbConnection(
new MySqlConnectionMock(new MySqlDbMock()),
MiniProfiler.Current);
using var intercepted = profiled.WithInterception(options =>
{
options.UseRecording();
options.UseLogging(Console.WriteLine);
});- Home
- Getting Started
- DotNet Fiddle Quick Start
- Provider Selection
- Providers and Compatibility
- ADO.NET and Dapper
- DbConnection Interception
- DI and Interception Setup
- Testing Strategy
- Diagnostics and Execution Plans
- Limitations and Known Gaps
- Recipes and Common Scenarios
- Transactions and Volatile Data
- Schema Snapshots and Replay
- FAQ and Troubleshooting
- Observability and Debugging
- Benchmark Results
- Provider-Specific Recipes
- Examples by Architecture
- Migration from Real DB Tests
- Performance of Test Suites
- Compatibility Matrix Summary
- Glossary
- Extensions and Ecosystem
- ORM and Test Integrations
- MiniProfiler Integration
- Visual Studio Extension
- VS Code Extension
- Maintainer Resources
- Início
- Começando
- Começando no .NET Fiddle
- Escolha do Provider
- Provedores e Compatibilidade
- ADO.NET e Dapper
- Interceptação de DbConnection
- Setup de DI e Interceptação
- Estratégia de Testes
- Diagnóstico e Planos de Execução
- Limitações e Gaps Conhecidos
- Receitas e Cenários Comuns
- Transações e Dados Voláteis
- Snapshots de Schema e Replay
- FAQ e Troubleshooting