2012-04-20 27 views
3

我用黃瓜同廠女孩,這裏是神祕的問題對象沒有找到,工廠女孩創建對象,但在數據庫

在我的黃瓜步驟

fact = Factory.create(:fact, 
        :factable_type => "type_#{i}", 
        :factable_id => i.to_s, 
        :factable_action => "action_#{i}", 
        :priority => "1" 
    ) 

當我在調試模式下檢查紅寶石礦我有一個事實,一個ID,但如果我查一下我的IRB測試控制檯:

ruby-1.9.2-p180 :011 > Fact.all 
=> [] 

當然,當我想運行我的測試和檢查數據庫中的對象的存在,我的測試失敗正因爲如此。你有什麼主意嗎 ?

這裏是我的env.rb文件:

# IMPORTANT: This file is generated by cucumber-rails - edit at your own peril. 
# It is recommended to regenerate this file in the future when you upgrade to a 
# newer version of cucumber-rails. Consider adding your own code to a new file 
# instead of editing this one. Cucumber will automatically load all features/**/*.rb 
# files. 

require 'cucumber/rails' 
require 'fakeweb' 
require "factory_girl" 

# Add this to load Capybara integration: 
require 'capybara/rspec' 
require 'capybara/rails' 

require File.expand_path('../../../spec/vcr_setup.rb', __FILE__) 
require 'cucumber/rails' 
require 'cucumber/rspec/doubles' 

require 'email_spec' 
require 'email_spec/cucumber' 

# require 'cucumber/thinking_sphinx/external_world' 
# Cucumber::ThinkingSphinx::ExternalWorld.new 

# Capybara defaults to XPath selectors rather than Webrat's default of CSS3. In 
# order to ease the transition to Capybara we set the default here. If you'd 
# prefer to use XPath just remove this line and adjust any selectors in your 
# steps to use the XPath syntax. 
Capybara.default_selector = :css 

Capybara.run_server = true #Whether start server when testing 
Capybara.default_selector = :xpath #default selector , you can change to :css 
Capybara.default_wait_time = 2 #When we testing AJAX, we can set a default wait time 
Capybara.ignore_hidden_elements = false #Ignore hidden elements when testing, make helpful when you hide or show elements using javascript 
Capybara.javascript_driver = :culerity #default driver when you using @javascript tag 

# By default, any exception happening in your Rails application will bubble up 
# to Cucumber so that your scenario will fail. This is a different from how 
# your application behaves in the production environment, where an error page will 
# be rendered instead. 
# 
# Sometimes we want to override this default behaviour and allow Rails to rescue 
# exceptions and display an error page (just like when the app is running in production). 
# Typical scenarios where you want to do this is when you test your error pages. 
# There are two ways to allow Rails to rescue exceptions: 
# 
# 1) Tag your scenario (or feature) with @allow-rescue 
# 
# 2) Set the value below to true. Beware that doing this globally is not 
# recommended as it will mask a lot of errors for you! 
# 
ActionController::Base.allow_rescue = false 

# Remove/comment out the lines below if your app doesn't have a database. 
# For some databases (like MongoDB and CouchDB) you may need to use :truncation instead. 
#begin 
# DatabaseCleaner.strategy = :transaction 
#rescue NameError 
# raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it." 
#end 

# You may also want to configure DatabaseCleaner to use different strategies for certain features and scenarios. 
# See the DatabaseCleaner documentation for details. Example: 
# 
# Before('@no-txn,@selenium,@culerity,@celerity,@javascript') do 
#  DatabaseCleaner.strategy = :truncation, {:except => %w[widgets]} 
# end 
# 
# Before('[email protected]', '[email protected]', '[email protected]', '[email protected]', '[email protected]') do 
#  DatabaseCleaner.strategy = :transaction 
# end 
# 

## Sets up the Rails environment for Cucumber 
ENV["RAILS_ENV"] = "test" 
require File.expand_path(File.dirname(__FILE__) + '/../../config/environment') 
require 'cucumber/rails/world' 
Cucumber::Rails::World.use_transactional_fixtures 
# 
##Seed the DB 

Fixtures.reset_cache 

fixtures_to_load = ['facts','roles', 'user_types'] 

fixtures_folder = File.join(Rails.root, 'features', 'fixtures') 
fixtures = Dir[File.join(fixtures_folder, '*.yml')].map {|f| File.basename(f, '.yml') } 
fixtures.delete_if { |fx| !fixtures_to_load.index(fx)} 
Fixtures.create_fixtures(fixtures_folder, fixtures) 

Before do 
    Capybara.default_host = 'http://site.local' 

    NetworkConfig.initialize(:id => 1) 
end 

,在我factories.rb文件:

require "factory_girl" 

Factory.define :fact do |i| 
    i.factable_type "Follow" 
    i.factable_id "1" 
    i.factable_action  "create" 
    i.is_processed "false" 
    i.processing_has_started "false" 
    i.processing_has_ended "false" 
    i.priority "1" 
end 
+0

你是如何訪問irb的?紅寶石調試?鐵軌控制檯? – Spencer 2012-04-20 15:03:05

+0

當你說IRB你是指一個單獨的irb控制檯?如果是這樣,那麼這是正常的:因爲你在事務中包裝每個故事,所以其他數據庫連接看不到未提交的更改 – 2012-04-20 15:03:20

+0

您的Rails環境也可能是錯誤的。 – Spencer 2012-04-20 15:04:19

回答

0

如果您正在使用軌控制檯軌道Ç命令檢查來自您工廠的數據。我認爲你需要像這樣切換環境:

$ rails c 
irb(main):010>ActiveRecord::Base.establish_connection "test" 
irb(main):010> Fact.all