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
BeLowerCased() results in failing tests with only lower case characters. #1768
Comments
This is the description of the |
OK, yes I would argue that characters that have no upper or lower case definition would be excluded from the algorithm or approved, that's at least how I thought it would work. But if that's not the way it works, then that's not the way it works. Maybe I'm the first who stumble across this problem but perhaps this can be made clearer in the description of the function, just a thought? |
Hmm, I see your point. Wondering what @jnyrup thinks about that. |
I see that we did consider this in #1357 (comment) We probably should improve some documentation to stress that detail. |
I thought that anything that for instance had been var test = "ABC123".ToLower();
test.Should().BeLowerCased(); // ==> true Thanks for pointing me in the right direction regarding |
Let's keep it open so we update the documentation. |
Description
Just introduced using
BeLowerCased()
into one of our tests where we want to assert that a file path is lower case, but the result is not as expected. The response I get from the failing test is as follows:Perhaps the back slash is considered an upper case character in some way?
Complete minimal example reproducing the issue
Expected behavior:
Test to pass
Actual behavior:
Test fails
Versions
Fluentassertions: 6.3.0
.NET 5
The text was updated successfully, but these errors were encountered: