Debuggability: obtuse errors when window sizes change on different machines

[juliemr]

Make it easier to understand! Usually this manifests as something like 'element is not clickable at...'. It would be great to give users a better sense of what they can do to fix these issues.

[tyaga001]

Hi,

Is there any update on this issue? we are also facing this situation that most of the scripts are failing & error displays as element is not clickable on Jenkins while all are running on local.

error logs-

Failed: unknown error: Element is not clickable at point (583, 551). Other element would receive the click:
...
(Session info: chrome=52.0.2743.116) (Driver info: chromedriver=2.20.353145 (343b531d31eeb933ec778dbcf7081628a1396067),platform=Windows NT 10.0 x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 95 milliseconds Build info: version: '2.48.2', revision: '41bccdd', time: '2015-10-09 19:59:12' System info: host: 'P5-GL4JX52', ip: '10.209.170.39', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_92' Driver info: org.openqa.selenium.chrome.ChromeDriver Capabilities [{applicationCacheEnabled=false, rotatable=false, mobileEmulationEnabled=false, chrome={userDataDir=C:\Users\AppData\Local\Temp\scoped_dir22036_11818}, takesHeapSnapshot=true, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false, version=52.0.2743.116, platform=XP, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true}] Session ID: d0a7a3e67215f305bc239ed2645ab7b1

[heathkit]

Maybe better screenshot support would help here? Using something like the protractor-screenshoter-plugin would make debugging these kinds of issues easier. See also #3379

[benjaminapetersen]

@heathkit I'd def prefer improving the error message over having to go fishing around in screenshots. Seems like the kind of problem that should be able to be solved with error feedback.