#fluentassertions — Public Fediverse posts

Oh Mann, ich schreibe gerade alles um von FluentAssertions auf Shouldly...

#dotnet #fluentassertions #shouldly

Oh Mann, ich schreibe gerade alles um von FluentAssertions auf Shouldly...

#dotnet #fluentassertions #shouldly

Oh Mann, ich schreibe gerade alles um von FluentAssertions auf Shouldly...

#dotnet #fluentassertions #shouldly

@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!!!

@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.

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

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

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

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

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

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

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

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

@bradwilson @xunit A right, I forgot about that one. I have been an avid #FluentAssertions user since ages, so my knowledge about the #xUnit assertion landscape is a bit rusty.

(2 * 3).Should().Be(4);

#CodingArt #PippiLongstocking #FluentAssertions

(2 * 3).Should().Be(4);

#CodingArt #PippiLongstocking #FluentAssertions

(2 * 3).Should().Be(4);

#CodingArt #PippiLongstocking #FluentAssertions

Okay, I'm pretty happy with #xunit and #fluentassertions.

Check out this test: https://github.com/wadewegner/wordle-solver/blob/main/Tests/SuggestionEngineTests.cs#L30

First, I'm pleased with my cleverness when constructing a set of shorthand for building guesses to evaluate the responses.

Second, I love the syntax of FluentAssertions.

The task for the evenings this week is to update the #WebAPI workshop to #ASPNET7 and add a few new modules to it: #Hypermedia, Generating a client with #OpenAPI and Testing with #FluentAssertions

Getting ready for #Codemash in 23 days!! It will be fun doing a full-day workshop soon.

The task for the evenings this week is to update the #WebAPI workshop to #ASPNET7 and add a few new modules to it: #Hypermedia, Generating a client with #OpenAPI and Testing with #FluentAssertions

Getting ready for #Codemash in 23 days!! It will be fun doing a full-day workshop soon.

The task for the evenings this week is to update the #WebAPI workshop to #ASPNET7 and add a few new modules to it: #Hypermedia, Generating a client with #OpenAPI and Testing with #FluentAssertions

Getting ready for #Codemash in 23 days!! It will be fun doing a full-day workshop soon.

The task for the evenings this week is to update the #WebAPI workshop to #ASPNET7 and add a few new modules to it: #Hypermedia, Generating a client with #OpenAPI and Testing with #FluentAssertions

Getting ready for #Codemash in 23 days!! It will be fun doing a full-day workshop soon.

The task for the evenings this week is to update the #WebAPI workshop to #ASPNET7 and add a few new modules to it: #Hypermedia, Generating a client with #OpenAPI and Testing with #FluentAssertions

Getting ready for #Codemash in 23 days!! It will be fun doing a full-day workshop soon.