Closed ryanzec closed 11 years ago
At least css() and doesntExist() assertions are now failing under chrome. For the doesntExist(), the response that is returned is somehting like this:
{ "sessionId":"ada9b8843d491b0dda7ce53f62976ba8", "status":7, "value": { "message":"no such element\n (Session info: chrome=29.0.1547.57)\n (Driver info: chromedriver=0.7,platform=Mac OS X 10.8.4 x86_64)" } }
which would seems like it should pass since it says there is no such element. Not sure what the output for css() is.
Fixed with the latest release. Was related to changes in the newest Chromedriver.
At least css() and doesntExist() assertions are now failing under chrome. For the doesntExist(), the response that is returned is somehting like this:
which would seems like it should pass since it says there is no such element. Not sure what the output for css() is.