Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>According to Jnicklas (<a href="https://github.com/jnicklas/capybara" rel="nofollow">https://github.com/jnicklas/capybara</a>) you should move all Capybare specs you have in spec/requests to spec/features, since spec/features will now be used by Capybara 2.x. So this means that once you moved your Capybara specs to features, you could completely remove these specs from the spec/requests directory.</p> <p>Personally, I've finished the Ruby on Rails tutorial with no problems at all. I used Capybara 2.x and never used spec/features (just the 'old' spec/requests). For Rspec 2.x support you have to add require >'capybara/rspec'&lt; to your spec_helper.rb file. Without it, your tests could fail.</p> <p>Edit:</p> <p>I've just read trough the Rspec docs. If you are using Capybara in your specs these specs have to be moved to spec/features. If there is no Capybara involved the specs can simply stay in your requests directory.</p> <p>Feature specs <a href="https://www.relishapp.com/rspec/rspec-rails/v/2-12-2/docs/feature-specs/feature-spec" rel="nofollow">https://www.relishapp.com/rspec/rspec-rails/v/2-12-2/docs/feature-specs/feature-spec</a>!</p> <p>Request specs <a href="https://www.relishapp.com/rspec/rspec-rails/v/2-12-2/docs/request-specs" rel="nofollow">https://www.relishapp.com/rspec/rspec-rails/v/2-12-2/docs/request-specs</a></p> <p>More info, from Rubydoc: <a href="http://rubydoc.info/github/jnicklas/capybara/master#Using_Capybara_with_RSpec" rel="nofollow">http://rubydoc.info/github/jnicklas/capybara/master#Using_Capybara_with_RSpec</a></p>
    singulars
    1. This table or related slice is empty.
    1. POcapybara/rspec: should GET/PUT tests be in different files?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPeter de Ridder
    1. USPeter de Ridder
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThat should probably read "move all your _Capybara_ specs to spec/features".
      singulars
      1. PO
      1. USzetetic
    2. COYes, I know the capybara tests should be feature tests. But the problem still remains, should I split the above two tests into spec/features and spec/request?
      singulars
      1. PO
      1. USjsz
    3. COUpdated my questions. Hopefully it's more clear.
      singulars
      1. PO
      1. USjsz
 

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