Permalink
Commits on Oct 9, 2011
  1. bump to 2.7.0.rc1

    dchelimsky committed Oct 9, 2011
Commits on Oct 6, 2011
  1. ci: fix travis png url

    dchelimsky committed Oct 6, 2011
  2. Change matcher dups Enumerable before the action, supporting custom

    Enumerable types like CollectionProxy in Rails.
    
    - Closes rspec/rspec-rails#411
    dchelimsky committed Oct 6, 2011
Commits on Oct 4, 2011
Commits on Sep 30, 2011
Commits on Sep 27, 2011
  1. changelog

    - #91.
    dchelimsky committed Sep 27, 2011
  2. refactor: tease apart Have#matches?

    - #91.
    dchelimsky committed Sep 27, 2011
Commits on Aug 26, 2011
Commits on Aug 18, 2011
  1. Merge pull request #87 from moro/cover-matcher-documentation-typo-fix

    fix typo in 'cover' matchers documentation
    justinko committed Aug 18, 2011
  2. fix typo

    moro committed Aug 18, 2011
Commits on Jul 30, 2011
  1. if the sort fails, rescue and return the array as-is

    - Closes #81.
    - Closes #83.
    Peter van Hardenberg committed with dchelimsky Jul 30, 2011
Commits on Jul 14, 2011
Commits on Jul 2, 2011
  1. doc: tweaks

    dchelimsky committed Jul 2, 2011
Commits on Jun 23, 2011
  1. bump cukes to 1.0

    dchelimsky committed Jun 23, 2011
  2. dev: remove bin/ from git

    dchelimsky committed Jun 23, 2011
Commits on Jun 21, 2011
Commits on Jun 14, 2011
  1. doc: adjustments for yard

    dchelimsky committed Jun 14, 2011
  2. changelog

    dchelimsky committed Jun 14, 2011
  3. Merge pull request #77 from byroot/patch-1

    fix: missing underscores escaping in "have" feature description
    dchelimsky committed Jun 14, 2011
  4. doc: updates for yard

    dchelimsky committed Jun 14, 2011
Commits on Jun 13, 2011
Commits on Jun 11, 2011
  1. update binstubs

    dchelimsky committed Jun 11, 2011
  2. ignore yard artifacts

    dchelimsky committed Jun 11, 2011
  3. dev: remove rdoc dep

    dchelimsky committed Jun 11, 2011
  4. Improve the failure messages for the have/has predicate matcher.

    - For a case like `foo.should have_some_stuff`, "expected #has_some_stuff? to..." is better than "expected #has_some_stuff?(nil) to...".  The nil is confusing since you didn't pass any arguments.
    - For a case like `foo.should have_each_of(:a, 7, "bar")`, "expected #has_each_of?(:a, 7, "bar")" is better than "expected #has_each_of?(:a)".  It's best to include all the arguments rather than just the first one.
    myronmarston committed Jun 11, 2011