Permalink
Commits on Aug 24, 2012
  1. Updated for 0.1.0

    zaphod42 committed Aug 24, 2012
Commits on Jul 29, 2012
  1. Document how to write matchers.

    zaphod42 committed Jul 29, 2012
  2. Improve the descriptions for #is

    The #is matcher was putting extraneous markers in when it was composed
    with other matchers. The markers were supposed to be there for when it
    needed to show the boundaries of a value. Since the description of other
    matchers should take care of that there is no need for the markers when
    it is just showing other matcher's descriptions.
    zaphod42 committed Jul 29, 2012
  3. Improve description from such_that

    The "such that" prefix on the #such_that matcher didn't help in the
    description when writing ad-hoc matchers. This removes that prefix,
    which should allow for more natural descriptions.
    zaphod42 committed Jul 29, 2012
  4. Allow chaining of match results

    This provides two new methods on match results: #or_else and #and_also.
    
    The #or_else method allows for converting mismatches into something
    else, which is useful when matching sub-components of larger objects.
    
    The #and_also method allows chaining a sequence of matches together and
    only continuing in the case of success. It stops on the first mismatch.
    zaphod42 committed Jul 29, 2012
  5. Split out gemspec

    By splitting the gemspec out of the Rakefile we should now be able to
    use Ramcrest as a gem directly from github.
    zaphod42 committed Jul 29, 2012
Commits on Jul 15, 2012
  1. Refactored out duplicate code in assert integrations

    Both the MiniTest integration and the RSpec integration had the same
    structure for matching. The only difference was how they dealt with
    failure.
    zaphod42 committed Jul 15, 2012
  2. Integrate with RSpec

    RSpec 2.11 adds the #expect method which provides a perfect extension
    point. The adds a #that method to the #expect interface so that you can
    use Ramcrest in RSpec using:
    
      expect(foo).that includes_in_any_order_exactly(is(2), is(4))
    zaphod42 committed Jul 15, 2012
Commits on Jul 4, 2012
  1. Fixing up the styling.

    Ah, the joy of using a styling system that I can't test easily locally.
    zaphod42 committed Jul 4, 2012
  2. Make MatchResult immutable

    Mutation scares me. Changing negate away from a mutating operation.
    zaphod42 committed Jul 4, 2012
Commits on Jul 2, 2012
  1. Merge pull request #4 from coreyhaines/eliminate_matcher_code_duplica…

    …tion
    
    Eliminate matcher code duplication
    zaphod42 committed Jul 2, 2012
Commits on Jul 1, 2012
  1. Some of the matchers were inconsistently including Match at bottom of…

    … class.
    
    Just cleaning up the code to be consistent.
    coreyhaines committed Jul 1, 2012
  2. Inject size matching into base enumerable matcher

    By controlling the size matching externally the base matcher can be used
    for both the exact includes matches as well as the subset includes
    matches.
    zaphod42 committed Jul 1, 2012
  3. Created includes matcher

    This matcher is used to match a subset of an enumerable.
    
    The implementation is horrible. Need to have some more matchers and
    compose to remove duplication.
    zaphod42 committed Jul 1, 2012