Web test fails randomly
I am getting random "The item was not found" errors when testing my web app. My test run will randomly fail at different locations in my test but always when trying to click this button. However, th...
Forum Discussion
Ok so.. need some extra help here. I figured out what went wrong, and I actually decided to re-start my automation building from scratch (afterall, the first go was mainly just learning the tool) with manually entering keywords instead of recording -- I am testing a web app with a huge number of dynamic elements, and it was reaking havoc on my namemapping file when just using the record feature.
With that said, how *would* I go about changing a situation like this in a namemap (my old project was like this)
Aliases.firefox.panelCon.cell1.Item1 -- this has 4 things underneath it.
Aliases.firefox.panelCon1.cell1.Item1 -- this has 5 things underneath it.
Aliases.firefox.panelCon2.cell1.Item1 -- this has 27 things underneath it.
I discovered a sneaky dynamic element that was used to identify the panelCon object. Now, I can fix that, but how exactly would I "move" the elements from panelCon1 and 2 to panelCon and fix my keyword tests in the process? Is that as long of a process as I think it is, or is there some sort of shortcut?
My new tests are running flawlessly, but just wondering how to do this for the future in case I get faced with this situation again.
Thanks!
With that said, how *would* I go about changing a situation like this in a namemap (my old project was like this)
Aliases.firefox.panelCon.cell1.Item1 -- this has 4 things underneath it.
Aliases.firefox.panelCon1.cell1.Item1 -- this has 5 things underneath it.
Aliases.firefox.panelCon2.cell1.Item1 -- this has 27 things underneath it.
I discovered a sneaky dynamic element that was used to identify the panelCon object. Now, I can fix that, but how exactly would I "move" the elements from panelCon1 and 2 to panelCon and fix my keyword tests in the process? Is that as long of a process as I think it is, or is there some sort of shortcut?
My new tests are running flawlessly, but just wondering how to do this for the future in case I get faced with this situation again.
Thanks!