-
Notifications
You must be signed in to change notification settings - Fork 6
/
README
103 lines (65 loc) · 3.16 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
= Remarkable ActiveRecord
Remarkable ActiveRecord is a collection of matchers to ActiveRecord. Why use
Remarkable?
* Matchers for all ActiveRecord validations, with support to all options. The only
exceptions are validate_format_of (which should be invoked as allow_values_for)
and the :on option;
* Matchers for all ActiveRecord associations. The only one which supports all
these options:
:through, :source, :source_type, :class_name, :foreign_key, :dependent,
:join_table, :uniq, :readonly, :validate, :autosave, :counter_cache, :polymorphic
Plus Arel scopes:
:select, :where, :include, :group, :having, :order, :limit, :offset
Besides in Remarkable 3.0 matchers became much smarter. Whenever :join_table
or :through is given as option, it checks if the given table exists. Whenever
:foreign_key or :counter_cache is given, it checks if the given column exists;
* Tests and more tests. We have a huge tests suite ready to run and tested in
ActiveRecord 2.1.2, 2.2.2 and 2.3.2;
* Great documentation;
* I18n.
== Installation
sudo gem install remarkable_activerecord --pre
Add this to your Gemfile:
group :test do
gem 'remarkable_activerecord', '>=4.0.0.alpha2'
end
Drop this into your spec/spec_helper.rb or spec/support/remarkable.rb file:
require 'remarkable/active_record'
This will also automatically load remarkable/active_model and add those matchers as well.
== Examples
All Remarkable macros can be accessed in two different ways. For those who prefer the Shoulda style, let’s look at some model tests:
describe Post do
should_belong_to :user
should_have_many :comments
should_have_and_belong_to_many :tags
should_validate_presence_of :body
should_validate_presence_of :title
should_validate_uniqueness_of :title, :allow_blank => true
end
For those who likes more the RSpec way can simply do:
describe Post do
it { should belong_to(:user) }
it { should have_many(:comments) }
it { should have_and_belong_to_many(:tags) }
it { should validate_presence_of(:body) }
it { should validate_presence_of(:title) }
it { should validate_uniqueness_of(:title, :allow_blank => true) }
end
== I18n
All matchers come with I18n support. If you want to translate your matchers,
grab make a copy of locale/en.yml and start to translate it.
Then add your new locale file to Remarkable in spec/support/remarkable.rb:
Remarkable.add_locale 'path/to/my_locale.yml'
And then:
Remarkable.locale = :my_locale
== Using it outside Rails
If you want to use Remarkable ActiveRecord outside Rails, you have to remember
a few things:
1. Internationalization is powered by the I18n gem. If you are using it with Rails,
it will use the built in gem, otherwise you will have to install the gem by hand:
gem sources -a http://gems.github.com
sudo gem install svenfuchs-i18n
2. Include the matchers. Remarkable Rails gem is the responsable to add
ActiveRecord matchers to rspec. If you are not using it, you have to do:
Remarkable.include_matchers!(Remarkable::ActiveRecord, RSpec::Core::ExampleGroup)
This will make ActiveRecord matchers available in all rspec example groups.