We’ve built our very first robots which is about to go to PROD (this weekend). One major issue that we are finding during testing that 7-10 times certain scripts pass. 3 times that they do not is due to “selector not found”. Since this is unattended robot, VPCs that this runs under are not accessible to developers (mimic PROD).
When adding screenshots to see it, we can see that the tree times it failed was due to fact that page loaded slower then 3 seconds. It is random on which activity it fails (and we have 200-300 activities in our script).
We have changed “on complete” to “on interactive” and vice versa. On some we’ve made a loop to keep checking.
Question: Shouldn’t “on complete” wait until element is completely painted before it tries selecting? Do you have better ideas?
Also, is there a global config variable to change default 3 seconds to maybe 10 before it gives up? I know there is also 30 second wait time, but it seems that activity is only waiting for 3.
What am I missing?
PS. Due to this, QA does not want to sign off until I have something more tangible to prove it’s not the script issue