As a side note...
If you are testing a web app in NS 4.7 and the content is w/ in a frame set (read as the URL doesn't change w/ navigation) and you resize the browser, NS 4.7 will reload the page and it will break your test.
The basic question to ask yourself is did you write your script in analog or context sensitive "mode". If you have analog statements - you're probably definitely screwed - however if you have context sensitive code you should be okay, in most cases. However, if the objects are not visible on the screen and you have to scroll down to see them on the smaller monitor than you're gonna have to do some extra scripting to make the tests less maintenance intensive next time. Add some code that checks the size of the window, checks for the objects existence prior to acting on them and if not present, build in a scroll action that makes sense to make the rest of the screen visible. The logic is gonna be determined by your web page design.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by turbotester: The basic question to ask yourself is did you write your script in analog or context sensitive "mode". If you have analog statements - you're probably definitely screwed.<HR></BLOCKQUOTE>
While that may indeed be true when attempting to run your script under differing screen resolutions, it has nothing to do with the physical size of the monitor.
The original poster wanted to change monitors from 17 inches to 14 inches. Unless he also changes resolutions, none of these problems should arise.
In addition, most tools record in context-level mode by default. And most of them don't require additional scrolling to find objects which aren't visible on the screen.
- Joe (email@example.com)
[This message has been edited by jstrazzere (edited 01-22-2003).]