davehunt/pytest-mozwebqa — pull request #71 by birdsarah (2012-09-23 11:17:06+00:00)
Title: Correct assert for chrome error message

This was causing testShouldErrorThatItCantFineTheChromeBinary to fail on my machine as follows:

> assert "Could not find Chrome binary at: foo" in failed[0].longrepr.reprcrash.message
E assert 'Could not find Chrome binary at: foo' in "WebDriverException: Message: 'ChromeDriver executable needs to be available in the path. Please downl...oogle.com/p/selenium/downloads/list and read up at http://code.google.com/p/selenium/wiki/ChromeDriver'"
E + where "WebDriverException: Message: 'ChromeDriver executable needs to be available in the path. Please downl...oogle.com/p/selenium/downloads/list and read up at http://code.google.com/p/selenium/wiki/ChromeDriver'" = .message
E + where = .reprcrash
E + where = .longrep

Looking at [selenium code on code.google.com](https://code.google.com/p/selenium/source/diff?path=/trunk/py/selenium/webdriver/chrome/service.py&format=side&r=11913&old_path=/trunk/py/selenium/webdriver/chrome/service.py&old=) the error message always appears to have started with ChromeDriver executable... so am wondering whether this is something to do with RC or another driver and we need to accomodate both....or perhaps there's a way to do this that doesn't test for a string.