Skip to content

Conversation

@NOtherDev
Copy link
Contributor

ShouldContainOnlyInOrder works only when the expected and actual collections have the same lengths. When expected is longer than actual, misleading ArgumentException is thrown instead of SpecificationException. When expected is shorter than actual, the assertion passes, but it shouldn't.

This pull requests fixes the method to cope with those scenarios, leaving the other method's characteristics not touched.

…as broken when the collections were of different lengths.
developwithpassion added a commit that referenced this pull request Jul 23, 2014
Fix for ShouldContainOnlyInOrder EnumerableAssertion extension that was broken when the collections were of different lengths
@developwithpassion developwithpassion merged commit faf6362 into developwithpassion:master Jul 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants