-
Assertion:
Assert.That(result.Count, Is.EqualTo(2));
can be replaced with:
result.Should().HaveCount(2);
now it replaced with:
result.Count.Should().Be(2);
-
### Description
There are two feeds (nuget.org) and an internal feed that both have different versions of `System.Windows.Interactivity`.
* The nuget.org package is deprecated (not sure if that …
-
### Description
We now have automatic code coverage as part of the CI pipeline, posting the result to https://coveralls.io/github/fluentassertions/fluentassertions
At the time of writing our lin…
-
Hej Søren :)
I would prefer to work with this if I could unpack an Option directly in the first Be() call, e.g.:
`customerIdOrNone.Should().Be("1234")`
The current version is quite verbose (bec…
-
### Description
This extension being widely used, I think it could benefit some unit testing.
It will make the implementation of new features and refactoring easier.
And why not migrate to .net 6 a…
-
Using FluentAssertions 5.10.0
This is just an idea and I'm probably an edge case user, but we love FluentAssertions over at the [Akka.NET project](https://github.com/akkadotnet).
We have a confi…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Package ecosystem
nuget
### Package manager version
_No response_
### Language version
_No response_
### …
-
Written on 19.03.2018 16:41:39
URL: http://asp.net-hacker.rocks/2017%2F09%2F27%2Ftesting-aspnetcore.html
-
### Discussed in https://github.com/fluentassertions/fluentassertions/discussions/1722
Originally posted by **rcdailey** October 27, 2021
When I have a `BeEquivalentTo()` comparison between tw…
-
Coming from XUnit + FluentAssertions, I must say I love the TestCase feature of NUnit.
At the same time I feel that the assertion syntax seems all over the place. The fluent attempt mostly applies …