Skip to content
Commits on Jul 21, 2014
  1. @cupakromer

    Add Rubocop style standards to build.

    cupakromer committed
    - Move custom excludes and non-ideal settings to .rubocop_todo.yml
    - Inherit the todo file from the main rubocop config
    - Add generic description about matcher module.
    
      We should consider moving the individual generator methods into this
      module. This will allow us to properly document the matchers as in
      rspec-expectations. We can also apply autoload if necessary at that
      point.
Commits on Apr 23, 2014
  1. @myronmarston

    Remove rspec-collection_matchers code.

    myronmarston committed
    rspec-collection_matchers provides all this functionality now.
Commits on Aug 10, 2013
  1. @dpogue @alindeman

    Change some version checks to use ActiveRecord.

    dpogue committed with alindeman
    This allow using ActiveRecord fixtures without pulling in all of Rails.
Commits on Jul 7, 2013
  1. @alindeman
  2. @alindeman

    Documentation updates

    alindeman committed
Commits on Jul 6, 2013
  1. @alindeman
Commits on Dec 4, 2012
  1. @ywen @alindeman

    `subject.should be_valid` works correctly with ActiveResource models

    ywen committed with alindeman
    * ... where valid? does not take an argument
    * Closes #648
Commits on Nov 28, 2012
  1. @jfirebaugh

    Don't assume ActiveModel is available

    jfirebaugh committed
    Like ActiveRecord, it is optional and its railtie may not
    have been required.
Commits on Nov 13, 2012
  1. @xentek
Commits on Sep 12, 2012
  1. @woahdae @alindeman

    Support validation contexts when using #errors_on

    woahdae committed with alindeman
    Previously, Model#errors_on calls Model#valid?, which will both clear
    the errors hash and run validations in the default context. This adds an
    :context option to #errors_on that gets passed to #valid?, allowing using
    errors_on with validation contexts.
    
    Exmaple usage:
    
        class Foo
          validates :name, length: {minimum: 20}, on: :publication
        end
    
        describe Foo
          it 'should have a name greater than 20 characters on publication' do
            subject.name = 'too short'
            subject.name.should have(1).error_on(:name, context: :publication)
          end
        end
Commits on Aug 18, 2012
  1. @jonhyman
Commits on Aug 6, 2012
  1. @myronmarston
  2. @myronmarston

    A better fix for CollectionProxy#should.

    myronmarston committed
    - Delay the fix so that users can configure a different expectation framework.
    - Handle the right class for rails 3.0 (AssociationProxy) and 3.1+ (CollectionProxy).
    
    - Fixes #588.
    - Fixes #445.
Commits on Aug 5, 2012
  1. @dchelimsky
Commits on Aug 3, 2012
  1. @dchelimsky

    Add should and should_not to CollectionProxy

    dchelimsky committed
    - Fixes #588.
    - Fixes #445.
Commits on Dec 8, 2011
  1. @dchelimsky

    more rdoc cleanup

    dchelimsky committed
Commits on Nov 22, 2011
  1. @dchelimsky
  2. @dchelimsky

    small rdoc tweak

    dchelimsky committed
Commits on Oct 16, 2011
  1. @dchelimsky

    cleanup and add some rdoc

    dchelimsky committed
Commits on Nov 6, 2010
  1. @dchelimsky

    just ask if AR is defined instead

    dchelimsky committed
    - Closes #254.
  2. @dchelimsky

    Move error[s]_on to ActiveModel::Validations so it can be used by other

    dchelimsky committed
    ActiveModel compliant ORMs
    
    - Closes #251.
Commits on Sep 5, 2010
  1. @dchelimsky

    Use Rails config to determine whether or not we're using AR

    dchelimsky committed
    - defined?(:ActiveRecord) is unreliable
Commits on Jul 24, 2010
  1. @dchelimsky
Commits on Jul 18, 2010
  1. @dchelimsky

    cleanup whitespace

    dchelimsky committed
Commits on May 17, 2010
  1. @dchelimsky
Commits on Apr 28, 2010
  1. @dchelimsky
Something went wrong with that request. Please try again.