containsInAnyOrder has different behaviour depending on order of required elements in iterable to match

liangzai-cool / hamcrest

Automatically exported from code.google.com/p/hamcrest

0 stars 0 forks source link

containsInAnyOrder has different behaviour depending on order of required elements in iterable to match #64

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

containsInAnyOrder's matcher will succeed if the iterable to match contains
more than the matched elements, but only one of the matched elements is the
last element in the iterable to match.

The attached test passes, and clearly should not.

Original issue reported on code.google.com by s.c.si...@gmail.com on 19 Feb 2009 at 3:34

Attachments:

ContainsInAnyOrderTest.java

GoogleCodeExporter commented 9 years ago

Duplicate of Issue 59

Original comment by smgfree...@gmail.com on 27 Feb 2009 at 10:55

Changed state: Fixed
Added labels: 1.2RC5, Priority-Critical, Type-Defect

GoogleCodeExporter commented 9 years ago

Original comment by smgfree...@gmail.com on 21 Mar 2009 at 11:50

Added labels: 1.2RC4
Removed labels: 1.2RC5

GoogleCodeExporter commented 9 years ago

Original comment by smgfree...@gmail.com on 21 May 2009 at 10:44

Added labels: 1.2

GoogleCodeExporter commented 9 years ago

Original comment by smgfree...@gmail.com on 21 May 2009 at 10:45

Removed labels: 1.2RC4