Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The following answer is based on: <a href="https://stackoverflow.com/q/1506780/664833">How to run single test from rails test suite?</a> (stackoverflow)</p> <p>But very briefly, here's the answer:</p> <pre><code>ruby -I test test/functional/whatevertest.rb </code></pre> <p>For a <em>specific</em> <code>functional</code> test, run:</p> <pre><code>ruby -I test test/functional/whatevertest.rb -n test_should_get_index </code></pre> <p>Just put underscores in places of spaces in test names (as above), or quote the title as follows:</p> <pre><code>ruby -I test test/functional/whatevertest.rb -n 'test should get index' </code></pre> <p>Note that for <code>unit</code> tests just replace <code>functional</code> with <code>unit</code> in the examples above. And if you're using <strong>bundler</strong> to manage your application's gem dependencies, you'll have to execute the tests with <code>bundle exec</code> as follows:</p> <pre><code>bundle exec ruby -I test test/unit/specific_model_test.rb bundle exec ruby -I test test/unit/specific_model_test.rb -n test_divide_by_zero bundle exec ruby -I test test/unit/specific_model_test.rb -n 'test divide by zero' </code></pre> <p><strong>Most importantly</strong>, note that the argument to the <code>-n</code> switch is <em>the name of the test, and the word "test" prepended to it</em>, with spaces or underscores depending on whether you're quoting the name or not. The reason is that <code>test</code> is a convenience method. The following two methods are <em>equivalent</em>:</p> <pre><code>test "should get high" do assert true end def test_should_get_high assert true end </code></pre> <p>...and can be executed as <em>either</em> of the following (they are <em>equivalent</em>):</p> <pre><code>bundle exec ruby -I test test/integration/misc_test.rb -n 'test should get high' bundle exec ruby -I test test/integration/misc_test.rb -n test_should_get_high </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POrunning single rails unit/functional test
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USuser664833
    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
    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. VTUpMod
    1. COThanks that was helpfull. Standard directory is : test/functional/ instead of test/functionals/ so i edited your answer. Thanks
      singulars
      1. PO
      1. USvdaubry
    2. COOops.. thanks for the edit! I must have mistakenly slipped the _s_ in there because sometimes I execute just the functional tests via `bundle exec rake test:functionals`, which is plural. Note: same for running all unit tests.. just replace `functionals` with `units`.
      singulars
      1. PO
      1. USuser664833
    3. COThis did not work for me in Rails 3.0.7. It runs 0 tests.
      singulars
      1. PO
      1. USB Seven
 

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