-
Notifications
You must be signed in to change notification settings - Fork 3
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
Change after_hook error to use config not assume #42
Merged
Cruikshanks
merged 3 commits into
master
from
feature/config-immediate-exit-do-not-assume
Nov 28, 2016
Merged
Change after_hook error to use config not assume #42
Cruikshanks
merged 3 commits into
master
from
feature/config-immediate-exit-do-not-assume
Nov 28, 2016
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This will resolve issue #41, which highlights that **Quke's** assumption that CI is only being when the **phantomjs** driver is selected is restrictive and incorrect. Users may wish to use other drivers in a CI environment, for example [XVFB](https://en.wikipedia.org/wiki/Xvfb) with Chrome. Therefore this change removes the assumption in the `after_hook.rb` logic to fail immediately if **phantomjs** is being used, to instead drive the behaviour of a config flag.
Rubocop is essentially flagging what appear to be appropriate or reasonable statements and methods in the spec files. To make it clear that these are accepted not just overlooked, this change updates `.rubocop.yml` to match how we have actually structured the specs.
Cruikshanks
force-pushed
the
feature/config-immediate-exit-do-not-assume
branch
from
November 28, 2016 11:43
112fc66
to
697d949
Compare
This update gets the documentation stat to 100%.
Cruikshanks
force-pushed
the
feature/config-immediate-exit-do-not-assume
branch
from
November 28, 2016 11:53
697d949
to
a388ac5
Compare
This was referenced Nov 28, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will resolve issue #41, which highlights that Quke's assumption that CI is only being when the phantomjs driver is selected is restrictive and incorrect.
Users may wish to use other drivers in a CI environment, for example XVFB with Chrome. Therefore this change removes the assumption in the
after_hook.rb
logic to fail immediately if phantomjs is being used, to instead drive the behaviour off a config flag.