Databases
StackOverflow2013
Postsdbo
PORSpec assigns not working as expected
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORSpec assigns not working as expected
    primarykey
    data
    text
    <p>I have the following spec for the controller in simple ActiveRecord search feature:</p> <p>Spec:</p> <pre><code>it "returns the records that match the given due date" do create(:task, due_date: '2013-01-01') create(:task, due_date: '2014-01-01') get :search, 'filter' =&gt; { due_date: '2013-01-01' } expect(assigns(:tasks)).to \ eq Task.search('filter' =&gt; { due_date: '2013-01-01' }) end </code></pre> <p>The model and controller are simple:</p> <p>Model:</p> <pre><code> def self.search(params) result = self.all #I know this is a bad idea, but starting simple. params.each do |field, criteria| if field.match(/due_date|completed_date/) &amp;&amp; criteria != nil result = result.where("DATE(#{field}) = ?", criteria) end end result end </code></pre> <p>Controller action:</p> <pre><code> def search @tasks = Task.search(params['filter']) #output from when the spec runs below #puts params -&gt; {"filter"=&gt;{"due_date"=&gt;"2013-01-01"}, \ # "controller"=&gt;"tasks", \ # "action"=&gt;"search"} #puts params['filter] -&gt; {"due_date"=&gt;"2013-01-01"} #puts @tasks.inspect -&gt; just the one record render 'index' end </code></pre> <p>The spec fails, but it appears that it fails because the controller is returning both objects, while Task.search(...) is returning only the object with the specified value for <code>due_date</code>, as expected.</p> <p>Here is the error message (edited for length):</p> <pre><code> 2) TasksController GET #search returns the records that match the given due date Failure/Error: expect(assigns(:tasks)).to eq Task.search('filter' =&gt; { due_date: '2013-01-01' }) expected: #&lt;ActiveRecord::Relation [#&lt;Task id: 1, due_date: "2013-01-01 00:00:00", completed_date: "2013-12-22 03:57:37"&gt;, #&lt;Task id: 2, due_date: "2014-01-01 00:00:00", completed_date: "2013-12-22 03:57:37"&gt;]&gt; got: #&lt;ActiveRecord::Relation [#&lt;Task id: 1, due_date: "2013-01-01 00:00:00", completed_date: "2013-12-22 03:57:37"&gt;]&gt; </code></pre> <p>You would assume that since the model apparently works (as evidenced by this result and a separate model spec that passes) that there is something wrong with the controller, but the controller is dead simple. I also have a feature spec incorporating the same controller that submits a form, triggers the <code>search</code> action and looks at the output, and the output only includes the one, correct record.</p> <p>Am I missing something about how <code>assigns</code> works, making a dumb mistake or other?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSteve Rowley
    1. USSteve Rowley
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORSpec assigns not working as expected
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy not put some `logger.debug` traces in the controller to see what's really happening? The `where` clauses you're adding to the query are restricting the search, so if something in the `params` are not as you expect, you'd see too many records, as in fact you are seeing.
      singulars
      1. PORSpec assigns not working as expected
      1. USGene
    2. COThat's a good suggestion. I just used `puts` for the time being and edited the answer above. Supports the theory that the controller working as expected, contrary to the output of the spec.
      singulars
      1. PORSpec assigns not working as expected
      1. USSteve Rowley
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload