Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am using RSpec with a Rails engine without issues.</p> <p>I created my plugin using the following switches: -T --full --dummy-path=spec/dummy.</p> <ul> <li><code>-T</code> excludes test/unit</li> <li><code>--full</code> indicates that the plugin is an engine</li> <li><code>--dummy-path</code> is simply so that we don't get a test directory (the default is test/dummy).</li> </ul> <p>From there I used the spec_helper from the "start your engines" article:</p> <pre><code># Configure Rails Envinronment ENV["RAILS_ENV"] = "test" require File.expand_path("../dummy/config/environment.rb", __FILE__) require 'rspec/rails' ENGINE_RAILS_ROOT=File.join(File.dirname(__FILE__), '../') # Requires supporting ruby files with custom matchers and macros, etc, # in spec/support/ and its subdirectories. Dir[File.join(ENGINE_RAILS_ROOT, "spec/support/**/*.rb")].each {|f| require f } RSpec.configure do |config| config.use_transactional_fixtures = true end </code></pre> <p>For the generators. I add a config.generators block to my engine.rb file like so:</p> <pre><code>module MyEngine class Engine &lt; Rails::Engine config.generators do |g| g.test_framework :rspec, :view_specs =&gt; false end end end </code></pre> <p>With that, I'm able to get rspec tests when running a generator like the model generator.</p> <p>As for the DB, is your database.yml file set up correctly? Did you load the test environment, e.g. <code>rake db:test:clone</code> or <code>rake db:migrate RAILS_ENV=test</code>? My guess is that RSpec can't see your tables because there isn't a test database set up.</p>
    singulars
    1. This table or related slice is empty.
    1. POTesting Rails 3.1 mountable engine with Rspec
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USdwhite
    1. USdwhite
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTesting Rails 3.1 mountable engine with Rspec
      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. COshouldn't I use `--mountable` instead of `--full`?
      singulars
      1. PO
      1. USdeb
    2. COI followed the changes in your answer but I still can't use the generator. if I try `rails g integration_test posts` nothing happens. Maybe you left something out?
      singulars
      1. PO
      1. USdeb
    3. COI don't use the integration_test generator so I'm not sure. Just passing --full means that it is a standard engine non-namespaced and will generate the dummy project. I'm pretty sure you need to pass --full for a --mountable as well in order to get the dummy project to generate, but maybe that changed since the RC? What happens if you do a rails g model... or a controller?
      singulars
      1. PO
      1. USdwhite
 

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