Browsers - Chrome, Firefox
waitForElementPresent - //ul[@id=“tinterAlertList”]/li
If element is not present within 5-7 seconds, the recorder application stops executing the check for the element causing a very long, sometimes infinite test.
**After further examination in browser devtools it seems the following sequence of errors appear if the waitFor command executes multiple times without finding the element:
command-receiver.js:188 TypeError: sendResponse is not a function
at continueTestWhenConditionIsTrue (command-receiver.js:179) at command-receiver.js:184
command-receiver.js:191 Uncaught TypeError: sendResponse is not a function
at continueTestWhenConditionIsTrue (command-receiver.js:191) at command-receiver.js:184
My expectation is that, if I use a waitFor command, the command will wait for a certain amount of time and then continue execution as soon as the specified element is found, unfortunately this is not the case. Thank you for your help!