Add unit coverage for Microsoft.Extensions logging builder extensions - #11100
Conversation
Co-authored-by: Evangelink <11340282+Evangelink@users.noreply.github.com>
There was a problem hiding this comment.
Note
🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.
✅ 22/22 dimensions clean — no findings.
Notes: Single-file, test-only PR adding unit tests for MicrosoftExtensionsLoggingBuilderExtensions. Tests cover null-guard validation, configure-delegate and factory overload paths, log forwarding, disposal ownership semantics (owned vs. caller-owned factory), and LogLevel.None short-circuit behavior. Assertions use MSTest Assert (consistent with BannedSymbols.txt). Internal type casts (LoggingManager, TestApplicationBuilder) are valid via InternalsVisibleTo. Test helpers (CapturingLoggerFactory, CapturingLoggerProvider) are well-scoped as nested private classes.
🧵 Parallel-safety audit — PR #11100Nothing audited here touches process-global state, shared filesystem paths, or The PR adds one new self-contained test class, Audited Re-run with
|
🧪 Expert test review — PR #11100Reviewed the single new test file
This advisory comment was generated automatically. Grades are heuristic
|
Adds focused coverage for both
AddMicrosoftExtensionsLoggingoverloads, covering registration behavior at the MTP logging boundary.Argument validation
Disabled logging
LogLevel.Noneavoids configuring or using the MEL factory.Forwarding and lifetime
Fluent API