You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
h1. Summary
Whenever a user interacts with Scaffold's strongly typed elements, e.g. a click() or getText(), it uses the AbstractWebElement's protected getWebElement(boolean throwExceptionIfNotFound) method.
While this method does provide some error handling from other methods that use it, it doesn't provide any additional clues for cases where an element wasn't found due to some potential issue with javascript or an unforeseen error that is provided by the browser console.
We don't need to do anything too fancy right now. My thought behind this is that we can just let lombok report these errors as log.error when and if they exist during the protected getWebElement(boolean throwExceptionIfNotFound) catch block of a NoSuchElementException. Just this alone will enhance our error reporting for failed tests.
h1. A/C
Scaffold should report console errors when an element is interacted with in such a way that produces an exception
The text was updated successfully, but these errors were encountered:
h1. Summary
Whenever a user interacts with Scaffold's strongly typed elements, e.g. a click() or getText(), it uses the
AbstractWebElement
's protectedgetWebElement(boolean throwExceptionIfNotFound)
method.While this method does provide some error handling from other methods that use it, it doesn't provide any additional clues for cases where an element wasn't found due to some potential issue with javascript or an unforeseen error that is provided by the browser console.
This ticket is to add console log reporting. As noted in issue #8 , here is a stack overflow article that goes into detail on how we can pull logs: https://stackoverflow.com/questions/25431380/capturing-browser-logs-with-selenium-webdriver-using-java.
We don't need to do anything too fancy right now. My thought behind this is that we can just let lombok report these errors as
log.error
when and if they exist during the protectedgetWebElement(boolean throwExceptionIfNotFound)
catch block of aNoSuchElementException
. Just this alone will enhance our error reporting for failed tests.h1. A/C
The text was updated successfully, but these errors were encountered: