We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This test
[Test] public void EmptyCollectionsBug() { var actual = new List<string>(); var expected = new List<string>(); actual.Should().Equal(expected); }
Fails with the following message:
Expected collection to be equal to {empty}, but found empty collection.
I'm using the latest version (4.3.0)
The text was updated successfully, but these errors were encountered:
Hmm, you might have found an edge case (although I agree it's not that weird)
Sorry, something went wrong.
The thing is that it worked just fine with the previous version.
Yes, managed to reproduce it. Apparently there was no unit test for this scenario and something was refactored internally. Will fix it ASAP.
Comparing two empty collections resulted in a weird failure.
baaace8
Should solve #382
Fixed in 4.3.1
No branches or pull requests
This test
Fails with the following message:
I'm using the latest version (4.3.0)
The text was updated successfully, but these errors were encountered: