-
If the project being tested references Autofac 6.40 then a test project using FluentAssertions.Autofac 6.5.1 will fail.
But it just needs a redirect in the app.config:
…
-
**Before you file a bug, have you:**
* Tried upgrading to newest version of Fluent Assertions, to see if your issue has already been resolved and released? - yes
* Checked existing open *and* clos…
-
@amirrajan , at some point during the port to .NET Core, we decided to drop almost all assertion extensions from NSpec library, only a few remained: `IsTrue`, `IsFalse`, `ShouldBeTrue`, `ShouldBeFalse…
-
If I have an array property, the order of its values needs to be the same when asserting with `Should().BeEquivalentTo()`. I'm arguing that it shouldn't. That would be more in-line with "regular" Flue…
-
I get an error `error NU1008: Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items:...` multiple times, when…
-
### Description
When asserting on properties of type `ushort`, `short`, and `byte`, the failure message is slightly more difficult to read than with other unsigned number types.
### Reproduction…
-
### Description
I am updating the FluentAssertions package on a project from a very old version that would always do member-wise comparisons for `Should().BeEquivalentTo()`, even if the objects imp…
-
After updating to the latest FA, I found that our custom extension method conflicts with the one added in v6.4.0 [here](https://github.com/fluentassertions/fluentassertions/pull/1737).
The differen…
-
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
This repository currently has no…
-
# Bug report
**Describe the bug**
One test fails when run on liniux
**To Reproduce**
Steps to reproduce the behavior:
1. download and extract the sources for the latest release (beta 24 in …