Skip to content

Define url_options as per system test case does #2329

New issue

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

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

Already on GitHub? # to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

JonRowe
Copy link
Member

@JonRowe JonRowe commented May 9, 2020

Rails switched to manually defining url_options when they switched away from inheriting from integration test case.

See:
rails/rails@ea77dbf#diff-ff5f366a442b8761d35f94807700fa77R162

This should fix #2327

@JonRowe JonRowe marked this pull request as draft May 9, 2020 11:48
@benoittgt
Copy link
Member

I don't have anymore timeout with the PR, but I had no timeout with rspec-rails master too.
https://github.com/benoittgt/rspec_system_specs_bug

I think the problem is related to this:
Capture d’écran 2020-05-09 à 18 10 32

If you do :

--- a/Gemfile
+++ b/Gemfile
@@ -5,6 +5,9 @@ ruby '2.6.6'

 # Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
 gem 'rails', '6.0.0.rc1'
+gem 'actionpack', '6.0.0.rc1'
+gem 'activesupport', '6.0.0.rc1'
+gem 'railties', '6.0.0.rc1'

You do no have the timeout anymore. 🤔

@nnc
Copy link

nnc commented May 9, 2020

@benoittgt Rails 6.0.0.rc1 doesn't have the timeout issue because the problem was first introduced in Rails 6.0.1.rc1. Everything before that, including 6.0.0.rc1 is OK for me as well.

@benoittgt
Copy link
Member

@benoittgt Rails 6.0.0.rc1 doesn't have the timeout issue because the problem was first introduced in Rails 6.0.1.rc1. Everything before that, including 6.0.0.rc1 is OK for me as well.

Sorry... 🤦

@JonRowe JonRowe force-pushed the fix-system-examples-default-host branch 3 times, most recently from 443fa2b to 429160d Compare May 10, 2020 11:27
@@ -106,4 +106,4 @@ Feature: System spec
When I run `rspec spec/system/widget_system_spec.rb`
Then the output should contain "1 example, 0 failures"
And the output should not contain "starting Puma"
And the exit status should be 0
And the exit status should be 0 or I debug
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you understand why, I am interested. I wrote this #2325 (comment)

@JonRowe JonRowe force-pushed the fix-system-examples-default-host branch from 429160d to 7d0a9af Compare May 16, 2020 21:11
@JonRowe JonRowe force-pushed the fix-system-examples-default-host branch 2 times, most recently from 49b14cb to 0623e8a Compare May 25, 2020 14:45
@JonRowe JonRowe changed the base branch from master to main August 2, 2020 02:13
@JonRowe JonRowe force-pushed the fix-system-examples-default-host branch from 0623e8a to 1b0cc7b Compare December 24, 2021 07:11
@JonRowe JonRowe force-pushed the fix-system-examples-default-host branch from 1b0cc7b to 08182d3 Compare January 26, 2023 10:54
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

System specs broken with Rails 6.0.1+
3 participants