Capybara not working with action_cable

Question

I'm using the Rails 5 beta 3 with action cable, the integration works fine in development but when I try to run a feature test through capybara, it doesn't seem to hit the channel actions.

I'm using Portergeist and configured puma as capybara's server. Also I'm using es5-shim and es6-shim.

Has anyone else experienced this or knows any workaround?

Thanks!

Edit

Im using this capybara branch to configure Puma in Capybara

Capybara.register_server :puma do |app, port, host|
  require 'puma'
  Puma::Server.new(app).tap do |s|
    s.add_tcp_listener host, port
  end.run.join
end

I have not set anything on config.action_cable.allowed_request_origins

Also - what have you set config.action_cable.allowed_request_origins to in your test config — Thomas Walpole, Mar 09 '16 at 16:37
@TomWalpole I just edited my question. I think I'm using your capybara PR to configure Puma :). Also, config.action_cable.allowed_request_origins is not set. — Sergio D. Márquez, Mar 09 '16 at 17:13
ok -- rather than trying to configure allowed_request_origins in the test env with unknown ports, names, etc I just set `config.action_cable.disable_request_forgery_protection = true` in my test.rb - which allows connections from any location — Thomas Walpole, Mar 09 '16 at 17:21
From here: https://github.com/rails/rails/tree/master/actioncable#allowed-request-originse — Thomas Walpole, Mar 09 '16 at 17:31
How are you specifying the connection location for action cable? Are you using action_cable_meta_tag in your layout? Are you hardcoding in your JS? — Thomas Walpole, Mar 09 '16 at 17:33
I am using action_cable_meta_tag . Also configuring App.cable = ActionCable.createConsumer() just like that, without specifying an address. Please note that this configuration works fin in development mode — Sergio D. Márquez, Mar 09 '16 at 17:38
One last guess -- Did you specify Capybara.server = :puma ?? Without that the server would be registered but Capybara would still start webrick. If thats not it I would say say it's time to debug the browser connection and see whats happening -- (also I assumed you were using a JS capable driver with capybara - seems too simple but just verifying) — Thomas Walpole, Mar 09 '16 at 17:42
Yesss that was it! Can you add that response as an answer so I can mark it correct? — Sergio D. Márquez, Mar 09 '16 at 17:47

Thomas Walpole · Accepted Answer · 2016-03-09T18:45:51.427

12

For testing actioncable with Capybara you need to be using a multithreaded webserver. Since you're using a current pull request on Capybara that supports registering named drivers you will need to specify the named server to use

Capybara.server = :puma

For anyone not using the capybara branch with named servers you can do

Capybara.server {|app, port| 
  require 'puma'
  Puma::Server.new(app).tap do |s|
    s.add_tcp_listener Capybara.server_host, port
  end.run.join
}

edited Mar 09 '16 at 18:45

answered Mar 09 '16 at 17:51

Thomas Walpole

48,548
5
64
78

Thanks again. Hope your PR gets merged – Sergio D. Márquez Mar 09 '16 at 17:54
1

As the main developer of Capybara - I'm the one who determines when it gets merged :) I need to write documentation for it before I merge it – Thomas Walpole Mar 09 '16 at 17:55
1

@SergioMárquez I somehow accidentally down voted your question -- could you edit it slightly so I can remove that vote – Thomas Walpole Mar 09 '16 at 18:14
lol, I didn´t realize that! Thanks for your harddd work then. Capybara is awesome! I eddited my question – Sergio D. Márquez Mar 09 '16 at 18:41
1

Where should I put this capybara configuration? – Mario Mar 14 '16 at 17:45
1

@marcpt Wherever you're configuring Capybara -- usually rails_helper.rb or spec_helper.rb -- -If you're using the Capybara master branch you can just specify `Capybara.server = :puma` now. – Thomas Walpole Mar 14 '16 at 19:03

NickGnd · Answer 2 · 2016-07-04T14:17:47.210

6

From Capybara v2.7.0 passing a block to Capybara::server is deprecated (commit).

Deprecation message: DEPRECATED: Passing a block to Capybara::server is deprecated, please use Capybara::register_server instead

To register new web server (for example puma) use:

  Capybara.register_server :puma do |app, port, host|
    require 'puma'
    Puma::Server.new(app).tap do |s|
      s.add_tcp_listener host, port
    end.run.join
  end

Link to documentation

edited Jul 04 '16 at 14:17

answered Jul 04 '16 at 14:02

NickGnd

5,107
1
20
26

in v2.7.0, puma is already a registered webserver. Capybara.server = :puma will work just fine. – awilkening Sep 27 '16 at 21:35

Capybara not working with action_cable

2 Answers2

Linked