Skip to content
New issue

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

Bug when comparing two empty collections. #382

Closed
dmytro-gokun opened this issue Apr 1, 2016 · 4 comments
Closed

Bug when comparing two empty collections. #382

dmytro-gokun opened this issue Apr 1, 2016 · 4 comments

Comments

@dmytro-gokun
Copy link

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)

@dennisdoomen
Copy link
Member

Hmm, you might have found an edge case (although I agree it's not that weird)

@dmytro-gokun
Copy link
Author

The thing is that it worked just fine with the previous version.

@dennisdoomen
Copy link
Member

Yes, managed to reproduce it. Apparently there was no unit test for this scenario and something was refactored internally. Will fix it ASAP.

@dennisdoomen
Copy link
Member

Fixed in 4.3.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants