drewbourne/hamcrest-as3

Issues

• containsString, endsWith, startsWith should have an option caseinsensitive

  #24 opened 15 years ago by jeromedecoster
  3

• assert undefined

  #56 opened 10 years ago by Kalinovych
  0

• hasItems should split Array

  #54 opened 12 years ago by judoole
  0

• A more readable solution of using describeAs?

  #52 opened 13 years ago by karfau
  0

• Description could be completely wrong for Matcher that execute a closure

  #48 opened 13 years ago by karfau
  4

• Check Code/Docs for "exclusive" and "inclusive" in package org.hamcrest.number

  #47 opened 13 years ago by karfau
  1

• dateEqual result : not enough precision

  #49 opened 13 years ago by jeromedecoster
  2

• could containsString take an Array that test for existance of all elements?

  #38 opened 14 years ago by karfau
  3

• Refactoring idea

  #36 opened 14 years ago by jeromedecoster
  1

• ArrayMatchers doesn't work for Vectors (only 1.0.2, not in current source)

  #39 opened 14 years ago by karfau
  5

• Too many if in BaseDescription.as

  #25 opened 14 years ago by jeromedecoster
  1

• Aliases

  #41 opened 14 years ago by drewbourne
  1

• anyOf and allOf matchers should diagnose mismatches

  #46 opened 14 years ago by drewbourne
  1

• Problem with IsArraySizeMatcher for not iterable values

  #43 opened 14 years ago by karfau
  1

• Matcher suggestions

  #45 opened 14 years ago by drewbourne
  0

• TypeSafeDiagnosingMatcher incorrectly calls describeMismatch() with unsafe values

  #44 opened 14 years ago by drewbourne
  0

• isA() allow passing fully qualified Class name

  #42 opened 14 years ago by drewbourne
  0

• hasProperties() should include property mismatch description

  #40 opened 14 years ago by drewbourne
  1

• 2 new number matchers (test if a number is an interger or a float)

  #37 opened 14 years ago by jeromedecoster
  0

• MXML Matchers have cool options that pure as3 matchers don't have

  #34 opened 14 years ago by jeromedecoster
  1

• missing "ignoreCase" argument in StartsWith and EndsWith MXML matchers

  #35 opened 14 years ago by jeromedecoster
  1

• An example in README.markdown is wrong

  #33 opened 14 years ago by jeromedecoster
  1

• closeTo second argument has "bad" name

  #32 opened 14 years ago by jeromedecoster
  1

• IsNaN ans IsNotNaN matchers

  #31 opened 14 years ago by jeromedecoster
  1

• Failure message to handle non-simple types

  #30 opened 14 years ago by Ir0nClad
  1

• add MXMLMatchers for SortedBy and SortedByField

  #29 opened 15 years ago by drewbourne
  0

• hasProperties should support recursively checking properties

  #28 opened 15 years ago by drewbourne
  0

• itemIndexOf, itemLastIndexOf matchers

  #27 opened 15 years ago by jeromedecoster
  2

• MXMLMatchers should cache internal matcher instances

  #26 opened 15 years ago by drewbourne
  0

• hasProperty return a "bad" message

  #12 opened 15 years ago by jeromedecoster
  1

• hasPropertyWithValue javadoc is wrong

  #23 opened 15 years ago by jeromedecoster
  1

• dateBeforeOrEqual javadoc is wrong

  #22 opened 15 years ago by jeromedecoster
  1

• HasProperty should support property chains

  #19 opened 15 years ago by drewbourne
  1

• closeTo fails with decimal values

  #13 opened 15 years ago by jeromedecoster
  2

• EmptyString matcher is missing

  #17 opened 15 years ago by drewbourne
  1

• EveryItem should support Array-like Objects

  #18 opened 15 years ago by drewbourne
  1

• Support for AS3 Data Structures (as3ds) Datatypes

  #9 opened 15 years ago by timoxley
  1

• build-swc.sh has incorrect namespace

  #10 opened 15 years ago by drewbourne
  1

• containsString should diagnose mismatches

  #21 opened 15 years ago by drewbourne
  0

• greaterThan, lessThan return a "wrong" message

  #11 opened 15 years ago by jeromedecoster
  2

• add Unique matcher

  #20 opened 15 years ago by drewbourne
  0

• HasProperties should support MXML matchers for properties

  #16 opened 15 years ago by drewbourne
  0

• BaseMXMLMatcherContainer should invalidate itself if any of its children's 'matched' properties change

  #15 opened 15 years ago by drewbourne
  0

• BaseMXMLMatcherComposite should invalidate itself if it child 'matched' properties change

  #14 opened 15 years ago by drewbourne
  0

• suggested matcher: inArray(Array)

  #7 opened 15 years ago by drewbourne
  1

• Untitled

  #8 opened 15 years ago by timoxley
  2

• TypeSafeMatcher could give more information about failed matches

  #6 opened 15 years ago by wolever
  1

• The 'either' matcher seems suspiciously similar to the 'both' matcher...

  #4 opened 15 years ago by wolever
  2

• Coercing using 'as'

  #5 opened 15 years ago by wolever
  1

• No way to compare objects for similarity

  #3 opened 15 years ago by wolever
  5