by eValid » Mon Jan 07, 2013 12:15 pm
This can be a tough one, but there IS a solution. And it turns out to be very simple.
If the frame names vary over time, you really can't expect a static recording to adapt to changed frame names. No matter how you make your recording it will be "wrong" as soon as the frame names change.
eValid overcomes this by having a mode in which the recorded frame names are replaced by ordinal frame numbers. These numbers are assigned in the order in which the frames are openend.
We have found that this is very reliable in practice. We have not seen any applications which open frames in a different order unless, of course, the application has changed. And in that case a script that refers to frames in a different order from when the script was recorded is likely going to FAIL....but that is a good result in the sense that that particular failure is something that you WANT to know about...it is a true regression.
You'll find the switch to record tests using ordinal frame numbers rather than frame names in the Settings.
--eValid Technology Team