BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon New York

Find real-world practical inspiration from the world’s most innovative software leaders. Attend in-person.
QCon San Francisco

Learn what's next in software from world-class leaders pushing the boundaries. Attend in-person or get video-only pass to recordings.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News Debugging Tips for Selenium Test Failures

QCon San Francisco (Oct 2-6): Learn what's next from software leaders pushing the boundaries.

Debugging Tips for Selenium Test Failures

Leia em Português

Bookmarks

Jul 06, 2009 less than one minute

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more

While Selenium has gained wide acceptance as a useful tool for automating browser-level tests, tracking down the cause of test failures can take significant time. Daniel Wellman has shared two of his best tricks to greatly reduce debugging time for failed Selenium tests.

The first technique is to capture a screenshot any time a test fails. There are a couple of methods provided to support this: captureScreenshot, and captureScreenshotToString. The post Capture Screenshots of Selenium Failures, on the YouDevise Developer blog provides some example Java code for how this approach might be implemented.

The second technique is to capture the HTML DOM contents when a test fails. For this, Wellman recommends using the method getHtmlSource to capture the contents of the DOM and write them out to a file.

Taking the time to incorporate these two techniques could pay off handsomely in time saved debugging. This is not the first time that Wellman has written about the value of investing in your tools to gain more productivity. What improvements have you made to your toolset, testing or otherwise, that had big payoffs for you? Leave a comment and share with the InfoQ community.

Rate this Article

Adoption
Style

This content is in the Software Testing topic

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • More detail on capturing screenshots with Selenium

    by Phil Smith,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    There are a series of articles on the Cloud Testing Blog (blog.cloudtesting.com) about capturing screenshots with Selenium.

    The Cloud Testing service offers this all plus more with a Pay As You Test model - see www.cloudtesting.com/ for more details.

    Back to top
  • screenshot is often useless

    by Tomasz Kaczanowski,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I tried once to make screenshots but it was rather useless - you can see only the upper part of the web page which is often not enough

    i like the way WebTest Canoo does it

    Back to top
  • Re: screenshot is often useless

    by Phil Smith,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Hi Tomasz,

    You can capture the full browser window, as opposed to just the O/S window with Selenium for Firefox and IE with their native commands.

    Cloud Testing has extended this to also work with Safari, Opera and Chrome. This will hopefully be integrated back into the main Selenium release soon.

    See blog.cloudtesting.com/2009/06/24/capturing-scre... for more details.

    Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT