@maxitb @jonsagara another #opensource #dotnet project bites the dust. I get it that #opensourced projects where must be funded and sustainable somehow, but that's a terrible news. #fluentassertions and now #mediatr and #automapper 😔 that's just terrible.
Companies should pay for it, not developers!!!

https://github.com/kmtchl/FluentAssertionsToShoudlyConverter - Convert from #FluentAssertions to #Shouldly. Nice work https://github.com/kmtchl.

FluentAssertions 2/x

If you want to know exactly what "[7.0,8.0)" means, you'll find it here:

https://learn.microsoft.com/en-us/nuget/concepts/package-versioning?tabs=semver20sort#version-ranges

#FluentAssertions #dotnet #NuGet

If you are "unhappy" with license changes in FluentAssertions since version v8.0, you can force it to stay on v7.x.

.NET (Core), project file:

<code>
<ItemGroup>
<PackageReference Include="FluentAssertions" Version="[7.0,8.0)" />
</ItemGroup>
</code>

.NET Framework, packages.config:

<code>
<packages>
<package id="FluentAssertions" version="7.0.0" allowedVersions="[7,8)" targetFramework="net48" />
</packages>
</code>

Or just use Shouldly in future projects...

hth

#FluentAssertions #Shouldly #NuGet #UnitTesting #dotnet

@xunit @bradwilson Is there a way to assert the completion of a `Task<T>` with a timeout and then when the timeout is not hit assert on the result? Similar how it can be done in #FluentAssertions

`task.Should().CompleteWithinAsync(1.Seconds()).WithResult(expectedResult);`

https://fluentassertions.com/specialized/

#dotnet

re the #FluentAssertions changes is this correct and helpful?

#OSS #dotnet

Contributors to the #FluentAssertions library aren't happy either: https://github.com/fluentassertions/fluentassertions/pull/2943#issuecomment-2594782282

FluentAssertions v8.0 will cost $ 130,- per Developer.
Just watched Nicks video...

#dotnet #csharp #unittests #FluentAssertions

https://www.youtube.com/watch?v=ZFc6jcaM6Ms

Oh, so #FluentAssertions is changing the license in the new version 8. It doesn't seem like this is, well, particularly in line with what was there before?

https://github.com/fluentassertions/fluentassertions/pull/2943

#dotnet #testing #tdd

@ddoomen I am very grateful for all your private time (and probably nerves) you invested in #FluentAssertions for the last 15 years. Fluent Assertions has served us well for more than a decade and saved us a lot of time. I especially liked, how responsive and helpful you were when we had questions or feature requests on github and social media. I can only imagine how much work this is.

You have all my sympathies in your decision to monetize on this effort.

#dotnet

Whoa?! #FluentAssertions v8 dropping Apache #OSS license to claim $130 per seat 🤯 #DotNet

#FluentAssertions has been taken over by a hostile company. They have changed the license from Apache 2.0 to some bs commercial license, probably without consent from the contributors. I've created a fork, feel free to depend on it if you need a drop-in replacement that won't just change the license.

https://www.nuget.org/packages/AwesomeAssertions

#dotnet #nuget

🚀 Exciting Announcement! Fluent Assertions is partnering with Xceed Software Inc! This partnership will bring more resources and support, taking our project to new heights. Thanks to our amazing community for making this possible! #FluentAssertions #XceedSoftware #OpenSource #Innovation

FYI: #FluentAssertions by @ddoomen is going commercial.
It will stay free only for non-commercial use.

Discovered via this PR: https://github.com/fluentassertions/fluentassertions/pull/2944

FAQs are here https://xceed.com/fluent-assertions-faq/

#dotnet

...and tidy. We use #codingguidelines, automated style checkers, and auto-formatting tools to strive for that consistency. But the reality is that achieving complete #consistency is nearly impossible. Guidelines and #patterns evolve over time due to new insights, improved language features, or better frameworks. For example, in #FluentAssertions, we switched the naming conventions for tests from a "when-something-it-should-do-something" style to a more fact-based naming convention... (cont'd)

It took 8 months of refactoring, but I'm finally back at a green build again. #fluentassertions #v7

For version 7 of #FluentAssertions, we're redesigning the internal assertion API. Do you think `GetOrCreate` makes sense here?

In #dotnet #FluentAssertions is there a way to assert that two collections have the same items but ignoring the order **and using** `.Equals()` for the items?

I know there is

`.Should().BeEquivalentTo(enumerable, o => o.WithoutStrictOrdering())`

but that does not use `.Equals()` for the items. I would need

`.Should().Equal(enumerable, o => o.WithoutStrictOrdering())`

but that does not exist.

cc @ddoomen

As the capabilities of our #dotnet tool are expanding, so is the size of its test suite. Together with @ddoomen, it's time to enhance our #CSharp tests with #FluentAssertions.

https://www.youtube.com/watch?v=a_B4eLh2mdc

🎥 New video: #TDD: How Fluent Assertions came to be

Listen to
@LukeParkerDev
and
@ddoomen
explore #FluentAssertions and how it enhances unit #testing. 🧪 Discover TDD and open-source project tips! 🛠️

Watch now ⬇️

https://www.youtube.com/watch?v=sMWxVPMS4tg