test(phase-h.5): Extensions.Diagnostics + Extensions.Events TinyBDD coverage (~18 scenarios)#20
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #20 +/- ##
==========================================
+ Coverage 87.30% 87.48% +0.18%
==========================================
Files 291 291
Lines 8280 8280
Branches 1496 1496
==========================================
+ Hits 7229 7244 +15
+ Misses 713 694 -19
- Partials 338 342 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
JerrettDavis
force-pushed
the
feat/phase-h.5-diagnostics-events
branch
3 times, most recently
from
7ba0a43 to
67e5c3b
Compare
…ith ~18 TinyBDD scenarios - New test project: WorkflowFramework.Extensions.Diagnostics.Tests - TimingMiddlewareScenarios: 5 scenarios (TimingsKey constant, timing stored, multi-step timings, timing on throw, non-negative elapsed) - MetricsMiddlewareScenarios: 5 scenarios (initial state, increment TotalSteps, increment FailedSteps, AverageDuration positive, accumulation) - New test project: WorkflowFramework.Extensions.Events.Tests - InMemoryEventBusScenarios: 8 scenarios (no-sub goes to DeadLetters, subscriber delivery, not dead with subscriber, dispose unsubscribes, WaitForEvent resolves, timeout returns null, null throws, multiple subscribers) - All 18 scenarios green on net8.0, net9.0, net10.0 - Both projects added to WorkflowFramework.slnx Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
JerrettDavis
force-pushed
the
feat/phase-h.5-diagnostics-events
branch
from
67e5c3b to
ffbcb05
Compare
Code Coverage |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Changes
New:
tests/WorkflowFramework.Extensions.Diagnostics.Tests/TimingMiddlewareScenarios— 5 scenarios: TimingsKey constant value, timing stored in context, multi-step each get own entry, timing recorded even when step throws (finally block), elapsed is non-negativeMetricsMiddlewareScenarios— 5 scenarios: initial zero state, success increments TotalSteps, failure increments both counters, AverageDuration >= zero, 5 steps accumulate to 5New:
tests/WorkflowFramework.Extensions.Events.Tests/InMemoryEventBusScenarios— 8 scenarios: no-subscriber → DeadLetters, subscriber receives event, subscriber → not in DeadLetters, disposable unsubscribes, WaitForEventAsync resolves on match, timeout returns null, null event throws, multiple subscribers all receiveTest plan
dotnet testgreen on net8.0, net9.0, net10.0WorkflowFramework.slnx🤖 Generated with Claude Code