StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POBest way to test named scopes in Rails4
primarykey
Id
18912306
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-09-20T08:39:47.450
FavoriteCount
0
LastActivityDate
2013-09-20T14:58:35.267
LastEditDate
2013-09-20T08:48:17.277
LastEditorUserId
591644
OwnerUserId
591644
ParentId
0
PostTypeId
1
Score
0
ViewCount
682
LastEditorDisplayName
text
Body
As a part of the migration from Rails 3.2 to Rails 4, all named scopes need a proc block. Read more here: <a href="http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#active-record" rel="nofollow">http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#active-record</a> I had missed updating a scope in one of my models, which ended up biting me in production after my migration. So I wanted to figure out how to test this issue, and I found some strange behavior. In some cases the scopes appear to work fine without the proc, but not in other cases. <pre><code># models/offer.rb class Offer < ActiveRecord::Base scope :roster, where(:on_roster => true) scope :commit, where("status_id > 5") end </code></pre> If I use each scope option on independent calls in rails console, the queries are built properly and the results come back as one would have expected in Rails 3.2: <pre><code>$ rails c 2.0.0-p247 :001 > Offer.roster.all.size Offer Load (1.6ms) SELECT "offers".* FROM "offers" WHERE "offers"."on_roster" = 't' => 1 2.0.0-p247 :002 > Offer.commit.all.size Offer Load (1.6ms) SELECT "offers".* FROM "offers" WHERE (status_id > 5) => 3 </code></pre> However if I chain two scope calls together in the rails console, only the constraints from the last scope in the chain is included in each query: <pre><code>2.0.0-p247 :003 > Offer.roster.commit.all.size Offer Load (1.4ms) SELECT "offers".* FROM "offers" WHERE (status_id > 5) => 3 2.0.0-p247 :004 > Offer.commit.roster.all.size Offer Load (0.7ms) SELECT "offers".* FROM "offers" WHERE "offers"."on_roster" = 't' => 1 </code></pre> Now if I edit my model to add a proc to the second named scope, like so: <pre><code>class Offer < ActiveRecord::Base scope :roster, where(:on_roster => true) scope :commit, -> { where("status_id > 5") } end </code></pre> If the named scope with the proc defined is at the end of the chain, it will build the query with both sets of constraints. However, if the named scope without the proc defined is at the end of the chain, the resulting query is built without the constraints of the scope with the proc defined. <pre><code>$ rails c 2.0.0-p247 :003 > Offer.roster.commit.all.size Offer Load (1.4ms) SELECT "offers".* FROM "offers" WHERE "offers"."on_roster" = 't' AND (status_id > 5) => 0 2.0.0-p247 :004 > Offer.commit.roster.all.size Offer Load (0.7ms) SELECT "offers".* FROM "offers" WHERE "offers"."on_roster" = 't' => 1 </code></pre> So the first result is correct, and loads both scopes, but the second is incorrect and only loads the last scope. Then if you change both scopes to use procs, like so: <pre><code># models/offer.rb class Offer < ActiveRecord::Base scope :roster, -> { where(:on_roster => true) } scope :commit, -> { where("status_id > 5") } end </code></pre> You finally get the expected behavior: <pre><code>$ rails c 2.0.0-p247 :002 > Offer.roster.commit.all.size Offer Load (1.3ms) SELECT "offers".* FROM "offers" WHERE "offers"."on_roster" = 't' AND (status_id > 5) => 0 2.0.0-p247 :001 > Offer.commit.roster.all.size Offer Load (1.7ms) SELECT "offers".* FROM "offers" WHERE "offers"."on_roster" = 't' AND (status_id > 5) => 0 </code></pre> One note on this, calling <code>reload!</code> in the rails console will not update the behavior of the scopes after you've updated and saved your model. You have to end your rails console session and begin a new one to get the proc vs. non-proc to pick up correctly. The question I have is how to test to ensure that all of my scopes will behave as expected? Chaining scopes together each time I want to test whether they have a proc or lambda block seems very messy. However the simple tests I set up on the scopes, told me all my scopes were passing, and giving false positive results. Is there an easy way to test via Rspec with Rails4 whether the named scope resides within a proc or lambda block? 
Tags
<lambda><ruby-on-rails-4><rspec2><named-scope><proc>
Title
Best way to test named scopes in Rails4
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USPaul Pettengill
UserOwnerUserId
1. USPaul Pettengill
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

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.