|
|
Introduction
This page discusses some issues that arise when a page contains multiple frames,
possibly nested, and which are not named.
As the description of how eValid handles frame paths indicates, the path to a frame depends on the name of the frame and/or its nesting sequence. The naming convention used in eValid is described in the Frame Path Description.
Ordinal Frames Changing Order
If the frames on a page are not named, then evalid uses "ordinal numbers" to
keep track of them.
This is a reliable method as long as the order of frames remains the same
between script recording time and script playback time.
However, if the order changes -- for example, so that what was in Frame #1 at
record time now is in Frame #2 at playback time -- the script not longer uniquely
directs actions to the right frame.
Named Frames Changing Changing Structure
When frames are named there is less risk that the any change in the
order of frames causes a problem.
But this is NOT the case if named frames nesting change structure
between script recording time and script playback time.
In this case, while the user sees pages that appear to be completely meaningful,
automated test playback into a structure that has changed name-frame order cannot work reliably.
Frame Names Do Not Need To Be Unique
You don't need to have unique frame names, so long as the path from the top frame
(the main frame) is unique.
