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

GebReporting* fails when the browser is not on a HTML page (e.g. XML file) #126

Closed
geb-bot opened this issue Oct 24, 2011 · 3 comments
Closed
Assignees
Labels
Bug
Milestone

Comments

@geb-bot
Copy link

@geb-bot geb-bot commented Oct 24, 2011

Originally created by Christoph Neuroth.

When writeGebReport() tries to generate a Screenshot, Firefox refuses to take one and Selenium throws a WebDriver Exception. Also, when it tries to save the source, it fails with a NoSuchElementException.

Workaround override writeGebReport in a class extending GebReportingTest like this:

        try {
            super.writeGebReport()
        } catch (WebDriverException e) {
            log.warn('Could not take screenshot (maybe not on an HTML page?)', e)
        } catch (NoSuchElementException e) {
            log.warn('Could not save HTML (maybe not on an HTML page?)', e)
        }

(only tested with GebReportingTest, but will probably affect the others)

@geb-bot
Copy link
Author

@geb-bot geb-bot commented Oct 24, 2011

Originally posted by Luke Daley.

Thanks for the report.

We'll have to fix this in a more central way so we don't need to duplicate the logic in each test adapter.

@geb-bot
Copy link
Author

@geb-bot geb-bot commented Sep 13, 2012

Originally posted by Marcin Erdmann.

Fixed in geb/geb@50fb4e2

@geb-bot
Copy link
Author

@geb-bot geb-bot commented Sep 13, 2012

Resolved

@geb-bot geb-bot added the Bug label Apr 12, 2015
@geb-bot geb-bot added this to the 0.9.0 milestone Apr 12, 2015
@geb-bot geb-bot closed this Apr 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants