Improve BeUpperCased/BeLowerCased semantics#2660
Improve BeUpperCased/BeLowerCased semantics#2660dennisdoomen merged 14 commits intofluentassertions:developfrom
Conversation
Qodana for .NETIt seems all right 👌 No new problems were found according to the checks applied 💡 Qodana analysis was run in the pull request mode: only the changed files were checked Contact Qodana teamContact us at qodana-support@jetbrains.com
|
Pull Request Test Coverage Report for Build 9439983654Details
💛 - Coveralls |
dennisdoomen
left a comment
There was a problem hiding this comment.
Thanks for the great work. The basic changes are fine. Now we need to get the docs and naming right.
Also, consider using an IDE that has a spell checker built-in. It'll save you a lot of review comments.
Tests/FluentAssertions.Specs/Primitives/StringAssertionSpecs.BeUpperCased.cs
Outdated
Show resolved
Hide resolved
Tests/FluentAssertions.Specs/Primitives/StringAssertionSpecs.BeLowerCased.cs
Outdated
Show resolved
Hide resolved
Co-authored-by: Jonas Nyrup <jnyrup@users.noreply.github.com>
| // Assert | ||
| act.Should().Throw<XunitException>().WithMessage( | ||
| "Expected all characters in actual to be lower cased because we want to test the failure message, but found \"ABC\"."); | ||
| "Expected all alpha characters in actual to be lower cased because we want to test the failure message, but found \"ABC\"."); |
There was a problem hiding this comment.
"alpha" -> "alphabetic" in four tests to make the failing tests pass
There was a problem hiding this comment.
Doh! Thought I'd done that. Thanks.
Where can I see that in the build results?
…/drewjcooper/fluentassertions into beuppercased-belowercased
|
Breaking change? |
Yes, you're right. I've added the correct label. |
The PR changes the semantic of
BeUpperCased()andBeLowerCased()in line with the discussion in #2019.IMPORTANT
./build.sh --target spellcheckor.\build.ps1 --target spellcheckbefore pushing and check the good outcome