Controls Sometimes Do Not Match And Other Times Do - How Can I Keep The Controls Working?
When I ran my automation, the system would stop working and give an error that controls were not matched. When I ran the Interrogation tool, I got matches on all the fields but in practice, it didn't match. When i ran the interrogation a second time, the fields were not matched there either so I deleted them and started over. I got a match on interrogating the first time and then would not get a match when I interrogated the second time. I then went ahead and interrogated the page and made two sets of the same fields. Now, on several runs, I will get a match on one or the other (the example shows a match but it alternates which one it matches on during interrogation). On some runs, it will get no match at all. If I interrogate only once, it only matches the first time I interrogate and never again.
Is there some way I can make interrogation produce matches that will remain matched during the actual automation runs?
I foud a way to fix all this. If the child component is not found, I now rematch and that seems to work every time. I also got the username/password problem resolved by adding the "onkeyup" event after the value is entered. Now it finds the fields and logs in every time. :)
Keep up to date on this post and subscribe to comments