Repository navigation
Feature request: make a version from string BeEquivalentTo which ignores \n <> \r\n #1247
Description
Description
The currentBeEquivalentTo() method asserts that a string is exactly the same as another string, including any leading or trailing whitespace, with the exception of the casing.
It would be very useful to add a new method or extend this method to support also \n and \r\n.
Complete minimal example reproducing the issue
// Arrange
string expected= "foo\r\n";
// Act
string result = "foo\n";
// Assert
result.Should().BeEquivalentTo(expected);Expected behavior:
Assertion is OK
Actual behavior:
Assertion FAILS
Versions
- Latest version
Reacted by Daniel Betz, Mark Lopez, xzxzxc, Ivar Nesje, Peter Tandrup, SondreJAttensi, eolamisangoatote, Aleksandr Zadykian, Markus Schaber, Bibletoon and 6 more
Activity
markusschaber commentedon Jul 31, 2023
We could also use this.
Workaround: use
.Replace("\r\n","\n")on the strings in question before comparing.jimSampica commentedon Oct 2, 2023
This would be very useful when writing tests that are expected to pass cross-platform
dennisdoomen commentedon Oct 4, 2023
This is very similar to what is suggested here #2339 (comment)
riezebosch commentedon Dec 9, 2023
Was about to do this workaround an then I found out about this extension method I hadn't seen before: https://learn.microsoft.com/en-us/dotnet/api/system.string.replacelineendings?view=net-8.0 🥳
and it really is working for me (though I still would favour a more generic solution):
vbreuss commentedon Oct 26, 2024
Isn't this issue fixed with #2565 and should be closed?
Kryptos-FR commentedon Dec 4, 2024
It's not released yet apparently. It was in the alpha version but not in the release.
jnyrup commentedon Dec 4, 2024
See #2864 (comment)