測試反應的組分Rails中與水豚/菠菜

Question

我建立它採用反應的組分進行佈局一個Rails應用程序，在這裏你可以看到一個例子

.pure-g.homepage 
    = react_component("SectionA", {foo: @bar}, class: "pure-u-1") 
    = react_component("SectionB", {foo: @bar}, class: "pure-u-1") 
    = react_component("SectionC", {foo: @bar, foo2: @bar2, foo3: @bar3}, class: "pure-u-1") 

我triying菠菜對此進行測試，但它看起來像組件不在測試中呈現，我想知道是否有方法來測試與菠菜的React組件，如果有，我失蹤了什麼？

這裏是我的rails_helper.rb

# This file is copied to spec/ when you run 'rails generate rspec:install' 
require 'spec_helper' 
ENV['RAILS_ENV'] ||= 'test' 
require File.expand_path('../../config/environment', __FILE__) 
# Prevent database truncation if the environment is production 
abort("The Rails environment is running in production mode!") if Rails.env.production? 
require 'capybara/poltergeist' 
Capybara.javascript_driver = :poltergeist 
# Add additional requires below this line. Rails is not loaded until this point! 
require 'rspec/rails' 
require 'support/factory_girl' 

# Requires supporting ruby files with custom matchers and macros, etc, in 
# spec/support/ and its subdirectories. Files matching `spec/**/*_spec.rb` are 
# run as spec files by default. This means that files in spec/support that end 
# in _spec.rb will both be required and run as specs, causing the specs to be 
# run twice. It is recommended that you do not name files matching this glob to 
# end with _spec.rb. You can configure this pattern with the --pattern 
# option on the command line or in ~/.rspec, .rspec or `.rspec-local`. 
# 
# The following line is provided for convenience purposes. It has the downside 
# of increasing the boot-up time by auto-requiring all files in the support 
# directory. Alternatively, in the individual `*_spec.rb` files, manually 
# require only the support files necessary. 
# 
# Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f } 
Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f } 
# Checks for pending migration and applies them before tests are run. 
# If you are not using ActiveRecord, you can remove this line. 
ActiveRecord::Migration.maintain_test_schema! 

RSpec.configure do |config| 
    config.include RSpecFeaturesHelper, type: :feature 
    config.include Devise::TestHelpers, type: :controller 
    config.include ControllerHelpers, type: :controller 
    # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures 
    config.fixture_path = "#{::Rails.root}/spec/fixtures" 

    # If you're not using ActiveRecord, or you'd prefer not to run each of your 
    # examples within a transaction, remove the following line or assign false 
    # instead of true. 
    config.use_transactional_fixtures = false 

    # RSpec Rails can automatically mix in different behaviours to your tests 
    # based on their file location, for example enabling you to call `get` and 
    # `post` in specs under `spec/controllers`. 
    # 
    # You can disable this behaviour by removing the line below, and instead 
    # explicitly tag your specs with their type, e.g.: 
    # 
    #  RSpec.describe UsersController, :type => :controller do 
    #  # ... 
    #  end 
    # 
    # The different available types are documented in the features, such as in 
    # https://relishapp.com/rspec/rspec-rails/docs 
    config.infer_spec_type_from_file_location! 

    # Filter lines from Rails gems in backtraces. 
    config.filter_rails_from_backtrace! 
    # arbitrary gems may also be filtered via: 
    # config.filter_gems_from_backtrace("gem name") 
    <ReactOnRails::TestHelper class="configure_rspec_to_compile_assets"> 
    <config></config> 
    </ReactOnRails::TestHelper> 
end 

Answer 1

水豚包括RSpec的黃瓜基於對每個測試指定的元數據切換到Capybara.javascript_driver指定的驅動程序支持。雖然它沒有內置Spinach的支持。如果您希望能夠指定每個測試使用哪個驅動程序，則需要在執行鉤子之前實現兩個Cucumber的等效項 - https://github.com/teamcapybara/capybara/blob/master/lib/capybara/cucumber.rb#L17 - 用於Spinach，然後指定特定測試需要JS。如果你只是想所有的水豚驅動測試使用JS功能的驅動程序，你應該指定default_driver而不是javascript_driver

Capybara.default_driver = :poltergeist 

注：PhantomJS的當前發行版本 - 2.1.1（由鬼驅人使用）只支持ES5 max，因此爲了與React一起使用，需要確保所有的JS都被轉換爲ES5兼容。它支持的CSS也有限，基本上相當於一個7歲的瀏覽器。一個更好的（在JS/CSS支持方面）今天的解決方案是使用Chrome無頭與測試硒，如果採用最新的水豚，可以用

Capybara.default_driver = :selenium_chrome_headless