StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12368721
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-11T11:29:36.097
FavoriteCount
0
LastActivityDate
2014-01-20T08:22:52.420
LastEditDate
2014-01-20T08:22:52.420
LastEditorUserId
473040
OwnerUserId
473040
ParentId
7361036
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
referring to @danivovich example <pre><code>class Part < ActiveRecord::Base before_validation :strip_whitespace protected def strip_whitespace self.title = self.title.strip end end </code></pre> the proper way to write the spec is to separately write spec on strip_whitespace method and then just check if model class have callback set on it, like this:. <pre><code>describe Part do let(:record){ described_class.new } it{ described_class._validation_callbacks.select{|cb| cb.kind.eql?(:before)}.collect(&:filter).should include(:strip_whitespace) } #private methods describe :strip_whitespace do subject{ record.send(:strip_whitespace)} # I'm using send() because calling private method before{ record.stub(:title).and_return(' foo ') it "should strip white spaces" do subject.should eq 'foo' # or even shorter should eq 'foo' end end end </code></pre> if you need to skip callback behavior in some scenarios use <pre><code>before{ Part.skip_callback(:validation, :before, :strip_whitespace)} before{ Part.set_callback( :validation, :before, :strip_whitespace)} </code></pre> Update 20.01.2013 BTW I wrote a gem with RSpec matchers to test this <a href="https://github.com/equivalent/shoulda-matchers-callbacks" rel="nofollow">https://github.com/equivalent/shoulda-matchers-callbacks</a> In general I don't recommend callback at all. They are fine for example in this question, however once you do more complicated stuff like: After create-> <ul> <li>link account to user</li> <li>create notification</li> <li>send email to Admin</li> </ul> ...then you should create custom service object to deal with this and test them separately. <ul> <li><a href="http://railscasts.com/episodes/398-service-objects" rel="nofollow">http://railscasts.com/episodes/398-service-objects</a></li> <li><a href="http://blog.codeclimate.com/blog/2012/10/17/7-ways-to-decompose-fat-activerecord-models/" rel="nofollow">http://blog.codeclimate.com/blog/2012/10/17/7-ways-to-decompose-fat-activerecord-models/</a></li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORspec2 testing a before_validation method
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USequivalent8
UserOwnerUserId
1. USequivalent8
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.