PetrovS wrote:Afternoon:
What gives with tabbed browsing?
eValid doesn't have that?
Why not?
Thanks
Good questions PetrovS.
If you think about it, each time you "open a new tab" in a browser (IE, Chrome, etc.) what you really get is a new browser window.
But it's a "tab" in the sense that it's in the same browser face.
In the case of eValid, as a matter of simplification for testing purposes, new windows are NOT opened as tabs in the main browser face, but they are opened as entirely new windows.
The main window is "window 0" and all of the child windows are "window 1," window 2" etc. In any one session the value assigned only increases; if you close "window 3" and then open a new window after "window 4", it'll be called "window 5", etc.
The reason for this is to keep your TESTS coherent. The window number is put into the script command (usually as the second parameter), and the frame details of that window [if any] are put in the command also, if there is a need for it {this is command dependent}.
At the end of the day, the eValid method of keeping EVERY WINDOW SEPARATE leads to a much more rational and easy to understand functional test.
So in a multi-window test everything in any window/frame is always identified with a window number and a frame path (within that window).
-- eValid Support