Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The error is because you're passing an entire URL to a method that expects a name of one of the controller's action methods. If I understand correctly, you're trying to test several things at once.</p> <p>Testing that a route has a name is different from testing a route is different from testing a controller action. Here's how I test a controller action (this probably comes as no surprise). Note that I'm matching your naming, not recommending what I'd use.</p> <p>In spec/controllers/articles_controller_spec.rb,</p> <pre><code>describe ArticlesController do describe '#permalink' do it "renders the page" do # The action and its parameter are both named permalink get :permalink :permalink =&gt; 666 response.should be_success # etc. end end end </code></pre> <p>Here's how I test a named route with only rspec-rails:</p> <p>In spec/routing/articles_routing_spec.rb,</p> <pre><code>describe ArticlesController do describe 'permalink' do it 'has a named route' do articles_permalink(666).should == '/permalink/666' end it 'is routed to' do { :get =&gt; '/permalink/666' }.should route_to( :controller =&gt; 'articles', :action =&gt; 'permalink', :id =&gt; '666') end end end </code></pre> <p>Shoulda's route matcher is more succinct while still providing a nice description and failure message:</p> <pre><code>describe ArticlesController do describe 'permalink' do it 'has a named route' do articles_permalink(666).should == '/permalink/666' end it { should route(:get, '/permalink/666').to( :controller =&gt; 'articles', :action =&gt; 'permalink', :id =&gt; '666' }) end end </code></pre> <p>AFAIK neither RSpec nor Shoulda have a specific, concise way of testing named routes, but you could write your own matcher.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to call a Rails named route when testing controllers with RSpec?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDave Schweisguth
    1. USDave Schweisguth
    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. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COwith our first example I get a routing error, i need to test 'permalink/a_name'. Sorry my question was unclear. I need to test the permalink action, but I am using a named route. I need to know the right syntax for get ...
      singulars
      1. PO
      1. USrtacconi
    2. COWhen you test the action, don't worry about its route. Just test the action directly as in the first code example above. Testing the route is a different issue; see the other two examples for that.
      singulars
      1. PO
      1. USDave Schweisguth
    3. COyour first example does not work because a get is created having articles in the url, i.e. /articles/permalink/name_of_article but I need /permalink/name_of_the_article and RSpec does not allow me to do that.
      singulars
      1. PO
      1. USrtacconi
 

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