Issues

assert undefined
drewbourne/hamcrest-as3#56 · opened on Dec 5, 2014
hasItems should split Array
drewbourne/hamcrest-as3#54 · opened on Nov 2, 2012
A more readable solution of using describeAs?
drewbourne/hamcrest-as3#52 · opened on Mar 16, 2012
Matcher suggestions
drewbourne/hamcrest-as3#45 · opened on Feb 28, 2011
TypeSafeDiagnosingMatcher incorrectly calls describeMismatch() with unsafe values
drewbourne/hamcrest-as3#44 · opened on Feb 24, 2011
isA() allow passing fully qualified Class name
drewbourne/hamcrest-as3#42 · opened on Dec 22, 2010
2 new number matchers (test if a number is an interger or a float)
drewbourne/hamcrest-as3#37 · opened on Jul 22, 2010
MXML Matchers have cool options that pure as3 matchers don't have
drewbourne/hamcrest-as3#34 · opened on Jul 16, 2010
1
Failure message to handle non-simple types
drewbourne/hamcrest-as3#30 · opened on Jul 2, 2010
1
add MXMLMatchers for SortedBy and SortedByField
drewbourne/hamcrest-as3#29 · opened on Jun 7, 2010
hasProperties should support recursively checking properties
drewbourne/hamcrest-as3#28 · opened on Jun 4, 2010
itemIndexOf, itemLastIndexOf matchers
drewbourne/hamcrest-as3#27 · opened on Apr 29, 2010
2
MXMLMatchers should cache internal matcher instances
drewbourne/hamcrest-as3#26 · opened on Apr 21, 2010
containsString should diagnose mismatches
drewbourne/hamcrest-as3#21 · opened on Mar 30, 2010
add Unique matcher
drewbourne/hamcrest-as3#20 · opened on Mar 28, 2010
HasProperties should support MXML matchers for properties
drewbourne/hamcrest-as3#16 · opened on Mar 28, 2010
BaseMXMLMatcherContainer should invalidate itself if any of its children's 'matched' properties change
drewbourne/hamcrest-as3#15 · opened on Mar 28, 2010
BaseMXMLMatcherComposite should invalidate itself if it child 'matched' properties change
drewbourne/hamcrest-as3#14 · opened on Mar 28, 2010
TypeSafeMatcher could give more information about failed matches
drewbourne/hamcrest-as3#6 · opened on Aug 28, 2009
1