Databases
StackOverflow2013
Postsdbo
POInstance variable in view stays empty in Capybara test
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POInstance variable in view stays empty in Capybara test
    primarykey
    data
    text
    <p>I have a page that's rendering lots of stuff when I really use it, but renders nothing in Capybara. </p> <p>Controller goes like this:</p> <pre><code>class IdeasController &lt; ApplicationController def index @ideas = Idea.all end </code></pre> <p>Relevant bit of the page goes like this:</p> <pre><code>&lt;div class="accordion" id="accordion"&gt; Ideas length is &lt;%= @ideas.length %&gt;. &lt;% @ideas.each do |idea| %&gt; &lt;div class="accordion-group"&gt; &lt;div class="accordion-heading"&gt; &lt;%= link_to(idea.title, '#idea_' + idea.id.to_s, class: "accordion-toggle", data: {toggle: "collapse", parent: "#accordion"} ) %&gt; &lt;/div&gt; &lt;%= div_for(idea, class: "accordion-body collapse") do %&gt; &lt;div class="accordion-inner"&gt; &lt;%= render :partial =&gt; "idea", locals: { :idea =&gt; idea } %&gt; &lt;/div&gt; &lt;% end %&gt; &lt;/div&gt; &lt;% end %&gt; &lt;/div&gt; </code></pre> <p>When viewed in Development, this works beautifully and I get loads of stuff in the view (my db is full of mock data). But when I pop it open mid-test using <code>save_and_open_page</code>, it's completely empty, and says "Ideas length is 0".</p> <p>I did <code>rake db:test:clone</code> and <code>rake db:test:prepare</code>, but nada -- stays empty.</p> <p>Can you help me figure out why? Is there a way to peek into the test db and see if anything's there?</p> <p><strong>Edit:</strong> Inspired by the comments, I realized the trouble must be that the test environment flushes things out every time, so obviously there's nothing. In an (apparently misguided) attempt to resolve this, I did:</p> <pre><code> before do create(:idea) visit root_path click_link "Log In" end </code></pre> <p>Note the <code>create(:idea)</code> line, which was supposed to trigger my Idea factory and stick a mock idea into the db (the factory works fine with other tests).</p> <p>Now the page says:</p> <p>Internal Server Error</p> <p>SQLite3::BusyException: database is locked: INSERT INTO "users" ("created_at", "email", "name", "provider", "uid", "updated_at") VALUES (?, ?, ?, ?, ?, ?)</p> <p>which is beyond weird. <code>Rails s</code> is running in the background.</p> <p>As requested by commenter, full spec follows:</p> <pre><code>require 'spec_helper' describe "Idea page", js: true do subject { page } before do create(:idea) visit root_path click_link "Log In" end context "Single idea" do before do save_and_open_page #click_link('Eligendi sint quod quia alias sed sit vitae repellendus.') end it { should have_selector('a',text:'Claim') } end end </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USezuk
    1. USezuk
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COAre you creating Idea objects before your page is visited? Within a point in your test you can just do `p Idea.all` or `p Idea.count` to get that info outputted to your console. You can also use Pry, if you're using that gem. You can run `rails c test` to get in to the Rails console for the test environment.
      singulars
      1. POInstance variable in view stays empty in Capybara test
      1. USMrDanA
    2. CODo you use `database_cleaner` gem?
      singulars
      1. POInstance variable in view stays empty in Capybara test
      1. USdimuch
    3. COin your spec do: `puts Idea.all` to see if you have any Ideas. Also, it would help if you added your spec code to this question.
      singulars
      1. POInstance variable in view stays empty in Capybara test
      1. USipd
 

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