The Kronikol.Extensions.Oracle package adds Oracle operation tracking to your test diagrams using a DbConnection wrapping decorator pattern.

Why wrapping? Like SQLite, Oracle.ManagedDataAccess.Core does not emit DiagnosticSource events. This extension wraps OracleConnection with TrackingOracleConnection, which intercepts all command executions and transaction operations.

TrackingOracleConnection wraps a real OracleConnection and returns TrackingOracleCommand instances that intercept all 6 execution methods (ExecuteReader/NonQuery/Scalar × sync/async). TrackingOracleTransaction intercepts Begin/Commit/Rollback. All intercepted operations are classified by UnifiedSqlClassifier and logged to RequestResponseLogger.

dotnet add package Kronikol.Extensions.Oracle

services.AddOracleTestTracking(options =>
{
    options.Verbosity = SqlTrackingVerbosityLevel.Detailed;
});

This decorates all DbConnection registrations with a type-check guard — only OracleConnection instances are wrapped; others pass through unchanged.

var inner = new OracleConnection("...");
var tracked = inner.WithTestTracking(new OracleTrackingOptions
{
    Verbosity = SqlTrackingVerbosityLevel.Detailed
});

await tracked.OpenAsync();
// Use tracked as your DbConnection...

All options inherit from SqlTrackingOptionsBase.

TrackingOracleTransaction logs BEGIN TRANSACTION, COMMIT, and ROLLBACK operations automatically. These appear as separate arrows in the sequence diagram.

TrackingOracleCommand now captures response data from ExecuteReader and ExecuteScalar calls. Response arrows in diagrams show actual data instead of being empty. The ResponseDetail option controls the level of detail:

Set LogResponseContent = false to restore previous empty-arrow behaviour.