Skip to content

Check for puma and capybara when defining system tests #1893

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

Merged
merged 2 commits into from
Oct 25, 2017

Conversation

JonRowe
Copy link
Member

@JonRowe JonRowe commented Oct 22, 2017

Rather than skipping the definition altogether define a fake module that
warns about the dependencies.

Rather than skipping the definition altogether define a fake module that
warns about the dependencies.
…tests

As per @mockdeep's conversation in #1889 other dependencies might not
allow us to even load system_test_case so we fallback to our original
strategy for now.
@pat
Copy link

pat commented Oct 25, 2017

@JonRowe Just gave this a spin in a Rails app that doesn't have/need Capybara, and it didn't have any issues, nor did I see any warning (which is good, because I don't have any system tests).

@JonRowe
Copy link
Member Author

JonRowe commented Oct 25, 2017

Thanks so much @pat!

@JonRowe
Copy link
Member Author

JonRowe commented Oct 25, 2017

@myronmarston can you give me a quick sanity check in lieu of @samphippen (who's in hospital right now), as I'd like to release it to help rails devs

Copy link
Member

@myronmarston myronmarston left a comment

Choose a reason for hiding this comment

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

LGTM

@JonRowe JonRowe merged commit 074b158 into master Oct 25, 2017
@JonRowe JonRowe deleted the fix_system_tests_when_not_loaded branch October 25, 2017 22:31
JonRowe added a commit that referenced this pull request Nov 20, 2017
* Check for puma and capybara when defining system tests

Rather than skipping the definition altogether define a fake module that
warns about the dependencies.

* If we can't load system_test_case for some reason we cant run system tests

As per @mockdeep's conversation in #1889 other dependencies might not
allow us to even load system_test_case so we fallback to our original
strategy for now.
sebjacobs pushed a commit to futurelearn/rspec-rails that referenced this pull request Mar 15, 2019
* Check for puma and capybara when defining system tests

Rather than skipping the definition altogether define a fake module that
warns about the dependencies.

* If we can't load system_test_case for some reason we cant run system tests

As per @mockdeep's conversation in rspec#1889 other dependencies might not
allow us to even load system_test_case so we fallback to our original
strategy for now.
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

Successfully merging this pull request may close these issues.

3 participants