-
-
Notifications
You must be signed in to change notification settings - Fork 544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture design guidelines, principles and patterns #1340
Labels
Comments
dennisdoomen
changed the title
Capture design principles and patterns
Capture design guidelines, principles and patterns
May 11, 2021
5 tasks
5 tasks
5 tasks
5 tasks
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OccurenceConstraint
for usage in custom assertion extensions #1281 (comment)null
argumentsAndWhichConstraint
vsAndConstraint
.FailWith
vs throwing a normal .NET exception typeAndWhichConstraint<..., T>
theT
element must be fetched in way resilient to thatFailWith
don't throw immediately when encapsulated in a customAssertionScope
.E.g instead of
MyClassAssertions
thenMyClassAssertions<T> where T : MyClass
AssertionScope
soFailWith
does not halts execution and extra precautions must be taken to avoid e.g. enNullReferenceException
after verifying thatSubject is not null
predicate.Body
to format a predicate in a failure message. Just pass the predicate toFailWith
and let thePredicateLambdaExpressionValueFormatter
handle formatting it properlyWhen
andShould
in test names and use concise names likeExclusion_of_missing_members_works_with_mapping
[InlineData]
, unless:Should().NotThrow
in the assert.Code style
is null
andis not null
over!=/== null
The text was updated successfully, but these errors were encountered: