Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not sure exactly what you want to test, and I think there's some confusion as to what methods can be used where, so I'll try and give examples of <a href="https://www.relishapp.com/rspec/rspec-rails/v/2-13/docs/routing-specs">Routing specs</a>, <a href="https://www.relishapp.com/rspec/rspec-rails/v/2-13/docs/request-specs/request-spec">Request Specs</a>, <a href="https://www.relishapp.com/rspec/rspec-rails/v/2-13/docs/controller-specs">Controller specs</a>, and <a href="https://www.relishapp.com/rspec/rspec-rails/v/2-13/docs/feature-specs/feature-spec">Feature specs</a>, and hopefully one of them will be appropriate for you.</p> <h3>Routing</h3> <p>If you want to make sure that your root path gets routed to the <code>home#index</code> action, a routing spec may be appropriate:</p> <p><strong>spec/routing/routing_spec.rb</strong></p> <pre><code>describe "Routing" do it "routes / to home#index" do expect(get("/")).to route_to("home#index") end end </code></pre> <h3>Request</h3> <p>If you want to make sure that the <code>index</code> template gets rendered on a request to your root path, a request spec may be appropriate:</p> <p><strong>spec/requests/home_requests_spec.rb</strong></p> <pre><code>describe "Home requests" do it 'successfully renders the index template on GET /' do get "/" expect(response).to be_successful expect(response).to render_template(:index) end end </code></pre> <h3>Controller</h3> <p>If you want to make sure that the <code>index</code> template gets rendered on a request to the <code>index</code> action of your <code>HomeController</code>, a controller spec may be appropriate (and quite similar to a request spec in this case, but focused exclusively on the controller):</p> <p><strong>spec/controllers/home_controller_spec.rb</strong></p> <pre><code>describe HomeController do describe "GET index" do it "successfully renders the index template" do expect(controller).to receive(:index) # this line probably of dubious value get :index expect(response).to be_successful expect(response).to render_template(:index) end end end </code></pre> <h3>Feature</h3> <p>If you want to make sure the page rendered by <code>home#index</code> has some specific content, a feature spec may be appropriate (and also the only place you can use <a href="http://rubydoc.info/github/jnicklas/capybara/master">Capybara methods</a> like <code>visit</code>, depending on your Rails/RSpec version):</p> <p><strong>spec/features/home_features_spec.rb</strong></p> <pre><code>feature "Index page" do scenario "viewing the index page" do visit root_path expect(page).to have_text("Welcome to my awesome index page!") end end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PORspec / Capybara: Testing if a controller method is called
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaul Fioravanti
    1. USPaul Fioravanti
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORspec / Capybara: Testing if a controller method is called
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI see. So #should_receive works with #get but not #visit and must use the controller instance in HomeController. What I actually want to test is signing in through omniauth, which is why I want integration tests. The only thing I care about is that Sessions#create is called, and not where it is routed as I will redirect the user back to where he came from. It seems that the best thing is just to test the behavior in the Sessions#create method. Is that the most appropriate?
      singulars
      1. PO
      1. USuser2191332
    2. COThere's lots of similar questions about writing specs for Omniauth [on StackOverflow](http://stackoverflow.com/search?q=rspec+omniauth) and guides at [Railscasts](http://railscasts.com/episodes?search=omniauth) among others. Have a look through those resources and see what is right for you.
      singulars
      1. PO
      1. USPaul Fioravanti
    3. CO@user2191332 You should accept Paul Fioravanti's answer, It is a great one
      singulars
      1. PO
      1. USAndreas Lyngstad
 

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