Skip to content

Migrate to Shouldly #2450

@martincostello

Description

@martincostello

In light of the recent license changes to FluentAssertions, as well as the fact that we're now two versions behind due to breaking changes in v7, for future maintainability and to avoid licensing questions based on our usage of it, we should look to move to an alternative library providing similar/equivalent functionality that uses a standard open source license.

For example, Microsoft open source repositories are electing to not use v8 despite them themselves being open source. I'm not sure why specifically, other than an abundance of caution, but I've already seen examples of users asking questions to other open source repositories using FluentAssertions regarding licensing implications etc. The "easiest" thing to do to avoid such questions ourselves would be to just not use it.

A good candidate replacement for this is Shouldly, which I happen to already use as my assertion library of choice anyway.

I already took at look at doing this yesterday, but it was a big change (mostly in Polly.Specs), so it's best done on a per-project basis (or smaller) scope to reduce the size of change as FluentAssertions is removed.

The most impactful difference between the two seems to be the use of the Invoking() extension method.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions