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

Change after_hook error to use config not assume #42

Merged
merged 3 commits into from
Nov 28, 2016

Conversation

Cruikshanks
Copy link
Member

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.

@Cruikshanks Cruikshanks added the enhancement New feature or request label Nov 28, 2016
@Cruikshanks Cruikshanks self-assigned this Nov 28, 2016
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 Cruikshanks force-pushed the feature/config-immediate-exit-do-not-assume branch from 112fc66 to 697d949 Compare November 28, 2016 11:43
This update gets the documentation stat to 100%.
@Cruikshanks Cruikshanks force-pushed the feature/config-immediate-exit-do-not-assume branch from 697d949 to a388ac5 Compare November 28, 2016 11:53
@Cruikshanks Cruikshanks merged commit a78815d into master Nov 28, 2016
@Cruikshanks Cruikshanks deleted the feature/config-immediate-exit-do-not-assume branch November 28, 2016 11:54
Cruikshanks added a commit that referenced this pull request Nov 28, 2016
This change removes a focus label left in a test in the last PR #42, as per issue #43.

It also updates `.travis.yml` to add a new check for focus labels to attempt to prevent it happening again. If the check finds a match it will break the build.
Cruikshanks added a commit that referenced this pull request Nov 28, 2016
This change removes a focus label left in a test in the last PR #42, as per issue #43.

It also updates `.travis.yml` to add a new check for focus labels to attempt to prevent it happening again. If the check finds a match it will break the build.
Cruikshanks added a commit that referenced this pull request Nov 28, 2016
This change removes a focus label left in a test in the last PR #42, as per issue #43.

It also updates `.travis.yml` to add a new check for focus labels to attempt to prevent it happening again. If the check finds a match it will break the build.
Cruikshanks added a commit that referenced this pull request Nov 28, 2016
This change removes a focus label left in a test in the last PR #42, as per issue #43.

It also updates `.travis.yml` to add a new check for focus labels to attempt to prevent it happening again. If the check finds a match it will break the build.
Cruikshanks added a commit that referenced this pull request Nov 28, 2016
This change removes a focus label left in a test in the last PR #42, as per issue #43.

It also updates `.travis.yml` to add a new check for focus labels to attempt to prevent it happening again. If the check finds a match it will break the build.
Cruikshanks added a commit that referenced this pull request Nov 28, 2016
This change removes a focus label left in a test in the last PR #42, as per issue #43.

It also updates `.travis.yml` to add a new check for focus labels to attempt to prevent it happening again. If the check finds a match it will break the build.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant