Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Skip ActionDispatch::SystemTest integration possible? #1895

Closed
thenoseman opened this issue Oct 24, 2017 · 1 comment
Closed

[Question] Skip ActionDispatch::SystemTest integration possible? #1895

thenoseman opened this issue Oct 24, 2017 · 1 comment

Comments

@thenoseman
Copy link

Hi,
I was wondering if it is currently possible to skip the ActionDispatch::SystemTest integration when using Rails 5.1?

Usecase:
Our integrationtests require the server (puma/passenger) to run as a separate process.
The workflow while developing would be to start bin/rails server in one terminal tab and run a integration spec in the other.

When I activate rspec-rails 3.7.1 this doesn't work anymore since the ActionDispatch::SystemTest integration start the server itself.

As I understand the Integration is activated when requiring example.rb (https://github.com/rspec/rspec-rails/blob/master/lib/rspec/rails/example.rb#L11) and thus requiring 'rspec/rails/example/system_example_group'.

Is it possible to skip that to make the old way (two processes) work again?

Thanks!

@JonRowe
Copy link
Member

JonRowe commented Oct 25, 2017

Ironically someone had the inverse issue recently, they'd already turned off the inbuilt server and were having process configuration issues. I believe if you set Capybara.run_server = false you'll restore the behaviour you want. See #1813

@JonRowe JonRowe closed this as completed Oct 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants