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
EnumAssertions.Be()
doesn't identify the subject (but its NotBe()
counterpart does)
#1832
Comments
Also, I think the failure message for Actual current output in my tests:
|
You're right. That's better. |
We have a "not to be" or "to not be" discussion somewhere, but I can't find it right now. Just for the record, we're using "not to be" most places.
|
We should change that thing into a page on www.fluentassertions.com |
I decided to look at the source code after finding out that my
enum
assertions weren't identifying the subject name when usingBe()
, and yet it is identified correctly when usingNotBe()
.Apparently, in
EnumAssertions.Be()
(see line 60),{context:the enum}
was not being used:fluentassertions/Src/FluentAssertions/Primitives/EnumAssertions.cs
Lines 55 to 64 in 418a405
This doesn't match the counterpart
NotBe()
(see line 105):fluentassertions/Src/FluentAssertions/Primitives/EnumAssertions.cs
Lines 99 to 108 in 418a405
The above are permalinks but the issue currently exists in both the
develop
andmaster
branches.The text was updated successfully, but these errors were encountered: