Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

A collection of RSpec matchers for web apps.

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 lib
Octocat-spinner-32 spec
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 CHANGELOG.md
Octocat-spinner-32 Gemfile
Octocat-spinner-32 LICENSE
Octocat-spinner-32 README.markdown
Octocat-spinner-32 Rakefile
Octocat-spinner-32 remockable.gemspec
README.markdown

Remockable

Build Status Dependency Status Gem Version

A collection of RSpec 2 matchers to simplify your web app specs.

Note: Rails 3 support was dropped in version 0.2.

Background

The goal of this project is to provide a modern replacement to the now unmaintained Remarkable project. Remarkable was a great asset when Rails 2.3 was current, but a gap has been left by the unreleased Remarkable 4.0 since the release of Rails 3 and 4.

In looking at the code for Remarkable to determine the feasibility of continuing work on Remarkable itself, it seems clear that the scope of that project has outgrown its usefulness for most users. It was with this conclusion in mind that Remockable was born. It’s an attempt to start with a clean slate but maintain the original goal of Remarkable in spirit.

Installation

Add this line to your application’s Gemfile:

gem 'remockable'

And then execute:

$ bundle

Or install it yourself as:

$ gem install remockable

Usage

Remockable provides matchers for use with Active Model and Active Record classes.

Active Model Matchers

The following Active Model matchers are supported:

  • validate_acceptance_of
  • validate_confirmation_of
  • validate_exclusion_of
  • validate_format_of
  • validate_inclusion_of
  • validate_length_of
  • validate_numericality_of
  • validate_presence_of

Active Record Matchers

The following Active Record matchers are supported:

  • have_column
  • have_index
  • have_scope
  • have_default_scope
  • belong_to
  • have_one
  • have_many
  • have_and_belong_to_many
  • validate_associated
  • validate_uniqueness_of

Options

Options may be passed to the matchers in the same way they’re passed to the macros. For instance, when dealing with has_many :through associations, you could specify the following:

it { should have_many :subscriptions, through: :customers }

Contributing

  1. Fork it.
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Commit your changes (git commit -am 'Added some feature').
  4. Push to the branch (git push origin my-new-feature).
  5. Create a new Pull Request.

Copyright

Copyright © 2010-2013 Tyler Hunt. See LICENSE for details.

Something went wrong with that request. Please try again.