Replace FluentAssertions with Shouldly in Tests#1320
Closed
Kamyab7 wants to merge 1 commit intojasontaylordev:mainfrom
Kamyab7:main
Closed
Replace FluentAssertions with Shouldly in Tests#1320Kamyab7 wants to merge 1 commit intojasontaylordev:mainfrom Kamyab7:main
Kamyab7 wants to merge 1 commit intojasontaylordev:mainfrom
Kamyab7:main
Conversation
- Migrated all test assertions from FluentAssertions to Shouldly - Removed all FluentAssertions package references - Updated README to reflect use of Shouldly
This was referenced Apr 19, 2025
Owner
|
Thanks @Kamyab7 - would you mind pushing a new commit to trigger the CI again? I can't seem to trigger it here. |
Owner
|
See #1357 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request refactors all test projects to use Shouldly instead of FluentAssertions, which recently adopted a commercial license.
Changes included:
This helps keep the project free of commercial license concerns while maintaining clear, readable test assertions.
Closes #1309 .