What is the current behavior? (You can also link to an open issue here)
Currently, all assertions use the built-in Assert.Thing API that comes with xUnit.
What is the new behavior (if this is a feature change)?
With this change, all assertions in all unit tests have been migrated to Fluent Assertions. A dependency on Fluent Assertions has also been added to YarnSpinner.Tests.csproj.
By migrating to Fluent Assertions, our unit tests gain access to a richer and more expressive API for specifying the behaviour of our assertions, and have much better error messages when an assertion fails.
Does this pull request introduce a breaking change? (What changes might users need to make in their application due to this PR?)
This PR makes no user-facing changes, and only affects unit tests. All existing Assert.X assertions have been replaced one-for-one with their Fluent Assertions counterpart.
Please check if the pull request fulfills these requirements
[x] Tests for the changes have been added (for bug fixes / features)
[ ]
- Docs have been added / updated (for bug fixes / features)No user-facing behaviour changes[x] CHANGELOG.md has been updated to describe this change
What kind of change does this pull request introduce?
[ ] Bug Fix
[ ] Feature
[x] Something else
This PR migrates all tests to Fluent Assertions.
Currently, all assertions use the built-in
Assert.ThingAPI that comes with xUnit.With this change, all assertions in all unit tests have been migrated to Fluent Assertions. A dependency on Fluent Assertions has also been added to
YarnSpinner.Tests.csproj.By migrating to Fluent Assertions, our unit tests gain access to a richer and more expressive API for specifying the behaviour of our assertions, and have much better error messages when an assertion fails.
This PR makes no user-facing changes, and only affects unit tests. All existing
Assert.Xassertions have been replaced one-for-one with their Fluent Assertions counterpart.