-
Notifications
You must be signed in to change notification settings - Fork 731
Update PropertyInfoSelector assertions #1565
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
Update PropertyInfoSelector assertions #1565
Conversation
dennisdoomen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder whether it was worth the trouble. Especially since you're now directly testing the internal
Tests/FluentAssertions.Specs/Types/PropertyInfoSelectorAssertionSpecs.cs
Outdated
Show resolved
Hide resolved
jnyrup
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a single question, otherwise I like this approach 👍
| PropertyInfoSelector propertyInfoSelector; | ||
|
|
||
| // Act | ||
| Action act = () => propertyInfoSelector = new PropertyInfoSelector((Type)null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still uncomfortable directly using the "internal" types in tests, but we have no clear guidance on what we should and should not do.
More coverage of #1039
All these null reference exception paths.. already made me doubt TDD practices since a training on 27 Februari 2010 in Doorn 😉
IMPORTANT