Make poltergeist able to show debug web inspector #432
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
With the poltergeist_debug driver, you can now put 'page.driver.debug' in the cucumber step definitions and capybara will pause when it gets to the line and open a web inspector window of the tests in which you can see the errors.
This was referenced Jan 28, 2018
mi-wood
approved these changes
Jan 29, 2018
DeeDeeG
pushed a commit
to DeeDeeG/refugerestrooms
that referenced
this pull request
Oct 15, 2018
Make poltergeist able to show debug web inspector
DeeDeeG
pushed a commit
to DeeDeeG/refugerestrooms
that referenced
this pull request
Nov 3, 2018
Make poltergeist able to show debug web inspector
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.
With the poltergeist_debug driver, you can now put
page.driver.debugin the cucumber step definitions and capybara will pause when it gets to the line and open a web inspector window of the tests in which you can see the errors.In the opened browser page, click the bottom of the two links to get to a web inspector hooked up to the tests. Click the "console" tab to see any javascript errors. Click on the line number and you will be taken to the source javascript file with the line producing the error highlighted. Although, because of rails, all the javascript files are bundled into one giant file so it will take a while to load.
The inspector makes debugging the tests easier.
Context
Summary of Changes
:inspector => true.Screenshots