Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

CaptaiNiveau
Copy link

Hi!

I recently discovered your awesome testing libraries.
While trying the FluentAssertions nuget package, I couldn't compile them with Testably.Abstractions.
It seems to have a dependency on TestableIO.Abstractions, which break if said package isn't installed.
When I cloned the repo and added the project directly, everything worked as expected :)

However, instead of just asking for an update of the package, I tried updating/migrating it to the latest AwesomeAssertions version. I took the liberty to rename the project to AwesomeAssertions, since many other projects did the same.

Please take a look at my changes. The test suite ran successfully, though I'm not sure if my changes are to your standards (and if I did the migration to AssertionChain correctly).

Thank you for your effort!

@CaptaiNiveau
Copy link
Author

Ah, I'll look into the style convention of the PR message as well as commit messages

Copy link
Member

@vbreuss vbreuss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was an active contributor to Fluentassertions, but with their license changes abandoned the project (I am now using aweXpect instead).

So I also won't update this extension to Fluentassertions any longer. If you want, you can take it over and make it an extension for AwesomeAssertions, but maybe it would make more sense to move it there and rename it to e.g. AwesomeAssertions.Testably.Abstractions?

<ItemGroup>
<PackageReference Include="AwesomeAssertions" />
<PackageReference Include="Testably.Abstractions.Testing" />
<PackageReference Remove="AwesomeAssertions" />
Copy link
Member

@vbreuss vbreuss Sep 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should not need to add and remove AwesomeAssertions in the test project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants