如何调试rake规范不执行测试;无限悬挂问题(导轨3)

时间:2011-06-13 16:48:54

标签: ruby-on-rails-3 rake rspec-rails

使用rake 0.9.2,rspec,期望,模拟2.6.0,rspec-core 2.6.4,rspec-rails 2.6.1

当我执行rake rails或rspec spec path / to / spec时,我得到正常输出,直到我希望看到测试实际执行,然后没有进一步。我必须杀死进程kill-9%1来终止任务。

我的宝石文件:

source 'http://rubygems.org'

gem 'rails', '3.0.4'
gem 'rake', '0.9.2'

# Bundle edge Rails instead:
# gem 'rails', :git => 'git://github.com/rails/rails.git'

# gem 'sqlite3-ruby', :require => 'sqlite3'
gem 'warden'
gem 'devise', "= 1.2.1"
gem 'devise_invitable'
gem 'mysql'
gem 'will_paginate', "~> 3.0.pre2"
gem 'acts-as-taggable-on'
gem 'acts_as_list'
gem 'activemerchant'
gem 'braintree'
gem 'bartt-ssl_requirement', :require => 'ssl_requirement'
gem "paperclip"
gem 'jeditable-rails'
gem 'rdiscount'
gem "nifty-generators", :group => :development

gem "exception_notification", :git => "git://github.com/rails/exception_notification", :require => 'exception_notifier'

# Deploy with Capistrano
gem 'capistrano'
gem 'capistrano-ext'



# Bundle gems for the local environment. Make sure to
# put test-only gems in this group so their generators
# and rake tasks are available in development mode:
group :development, :test do
  gem 'webrat', ">=0.7.2"
  gem "rspec-rails"
  gem "ZenTest"
  #gem "autotest"
  #gem "autotest-rails"
  gem "cucumber",         :git => "git://github.com/cucumber/cucumber.git"
  gem "database_cleaner", :git => 'git://github.com/bmabey/database_cleaner.git'
  gem "cucumber-rails", ">= 0.3.2",   :git => "git://github.com/cucumber/cucumber-rails.git"
  gem 'factory_girl_rails'
  gem "capybara"
  #gem "capybara-envjs"
  gem "launchy"
  gem "spork"
  #gem "ruby-debug"
  gem "cancan"
end

shell的输出:

bill$ rake spec
/Users/bill/.rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.0/lib/bundler.rb:197: warning: Insecure world writable dir /opt in PATH, mode 040777
/Users/bill/.rvm/rubies/ruby-1.9.2-head/bin/ruby -S bundle exec rspec ./spec/controllers/products_controller_spec.rb ./spec/controllers/roles_controller_spec.rb ./spec/controllers/users_controller_spec.rb ./spec/models/product_spec.rb ./spec/models/role_spec.rb ./spec/models/user_spec.rb
/Users/bill/.rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.0/lib/bundler.rb:197: warning: Insecure world writable dir /opt in PATH, mode 040777
/Users/bill/.rvm/gems/ruby-1.9.2-head/gems/bundler-1.0.0/lib/bundler.rb:197: warning: Insecure world writable dir /opt in PATH, mode 040777

直到我杀了才进一步。使用--trace运行不提供任何其他信息。我敢肯定,我必须做一些简单愚蠢的事情。这似乎是从我最近的rake版本问题开始的,因此升级到rake 0.9.2,虽然我没有任何直接相关的具体证据。感谢您提供有关如何更好地调试此内容的任何建议。

3 个答案:

答案 0 :(得分:6)

呃,原来这是一个灯具文件的问题。我不使用它们,通常是工厂和存根,并且有一个规格不完整,所以看起来像rspec只是挂在那上面。我想通过缩小命令来测试不同的组,比如'rake spec:models',哪个有效,然后'rake spec:controllers'挂了。进入生成的规格并注意到加载灯具的线条,将它们移除并瞧瞧。永远不会沉闷...; - )

答案 1 :(得分:2)

更新:我从this question找到了解决问题的永久性解决方案。我将下面的行添加到config/environments/test.rb

config.active_record.maintain_test_schema = false

我遇到了同样的问题。一时兴起,我决定运行rake db:test:prepare,这似乎为我解决了,至少是暂时的。运行之后,我可以再次运行rake而不会发生任何事故,但如果我再次运行它,我会遇到与以前相同的问题。我现在似乎陷入了这个循环。 This article帮助阐明了这一主题,但我仍然不知道如何永久解决问题。

答案 2 :(得分:2)

对我而言,我在更新架构后修复了它:

bundle exec rake db:migrate

然后运行此命令:

bundle exec rake db:schema:load

手动检查schema.rb文件(如果已更新)。