The documentation https://docs.newrelic.com/docs/synthetics/new-relic-synthetics/scripting-monitors/synthetics-scripted-browser-reference-monitor-versions-050#structure for
$browser.waitForAndFindElement(locator: $driver.Locator [, timeout: number) indicates the timeout value is a default of 1000ms.
I have a script which indicates that the default is actually 10,000ms and anything less than this will not be honored, but values greater than 10000 will be honored. Is this known and as designed? If so, the docs need to be updated ASAP. If not, hopefully this can be logged as a bug and fixed?
I am in need of a way to try to find an element with potentially two different mutually exclusive xpaths. The hope was to try one way, fail quickly if not found and then try the second way. At this point, I cannot fail faster than 10s and with repeated calls to this I’m eating up a tremendous amount of my 180s budget.
Any ideas are appreciated!