dennisdoomen / fluentassertions / 24156118526

97%

develop: 97%

Build Type

push

github

Committed by dennisdoomen

Commit Message

Include nested scope failures in dry-run failure count

GetFailureCount() was only counting direct RegisterFailure() calls.
Failures from nested assertion scopes (e.g. via AssertionRuleEquivalencyStep)
are stored in assertionStrategy.FailureMessages rather than the local counter,
so they were invisible to TryToMatchCount — causing mismatches to look like
matches (count=0) and corrupting the optimal assignment.

Also call scope.Discard() after GetFailureCount() so that the dry-run scope
does not propagate its failure messages to the parent scope on disposal.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Coverage Stats

4037 of 4310 branches covered (93.67%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 2 files covered. (100.0%)

1 existing line in 1 file now uncovered.

13090 of 13314 relevant lines covered (98.32%)

67251.39 hits per line