Pin or remove fluentassertions

[SebastienDegodez]

Reason/Context

FluentAssertions (v8+) is changing license to become paid software for commercial use.

More details here

Description

Immediate solution without breaking:
Pin the NuGet version on the csproj
To achieve that we must surround the version number with []

Example:

<PackageVersion Include="FluentAssertions" Version="[7.0.0]" />

Implementation ideas

• Stay with v7 indefinitely
• Switch to alternative libs (shoudly?)
• Switch to builtin assert

[SebastienDegodez]

@lbroudoux more information to take decision : fluentassertions/fluentassertions#2943

[lbroudoux]

Thanks for pointing this one out. This is a critical topic.

From what I've read on the thread you mentioned, moving to v8 is not an option regarding the CNCF licensing policy. Sticking to v7 is not a mid/long-term option - we must just be sure we freeze to v7 the time we find a new alternative in a short term (no rush though).

We can either move to an alternative of the switch to built-in assertion - I have no real opinion on that as I can evaluate the required effort. We also should keep an eye on the project as a fork of fluentassertions v7 may also be launched if some maintainers are aligned with the project perspective ...

[SebastienDegodez]

I use FluentAssertion reflexively, the added value is debatable.

It's easy :) , some samples:

Fluent Assertion	XUnit	Notes
"microcks".Should().Be("microcks")	Assert.Equal("microcks", "microcks")	Or StrictEqual
"microcks".Should().NotBe("microcks")	Assert.NotEqual("microcks", "microcks")	Or NotStrictEqual
"microcks".Should().BeEquivalentTo("microcks")	Assert.Equivalent("microcks", "microcks")
Microcks.Should().NotBeNull()	Assert.NotNull(Microcks)
Microcks.Should().BeNull()	Assert.Null(Microcks)
Microcks.Should().BeEmpty()	Assert.Empty(Microcks)
Microcks.Should().BeNotBeEmpty()	Assert.NotEmpty(Microcks)