WinRunner scripts will need to be set up for both IE and NS. This is necessary as WinRunner captures a GUI map for each script (see MI doco for more info) and each browser produces a different GUI map.
What having 2 sets of scripts will do is allow the same test to be executed in both browsers.
IMHO, it is of marginal benefit to record in both browsers for cross browser testing as most browser compliance issues are easier for a human eye to pick up.
I Agree. The extra labor it takes to create and maintain a set of tests for multiple browser types is generally not work the cost. Concentrate on the browser that is used most frequently on your site and then create a small subset of tests for browser compatibility.
Ah, but if you are testing a public website, and have no specified client base that you could survey on what browser they use, then how do you know which one to concentrate on?
On the other hand, as was stated, I cannot see the benefit of maintaining a set of scripts for each browser. The ROI diminishes with each additional browser script recorded. So, I do agree with James.
If you can determine who would most likely be visiting the site, then you could probably guess which browser to test. For example, if it is a site with a lot of Linux/Unix stuff, then I would definitely concentrate on Netscape.
Thank u guys for ur replies. But how do i maintain a small subset of tests for browser compatibility. I mean what functions do i've to write in specific for browser compatibility.
thanx a lot guys
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by eswarqa: Thank u guys for ur replies. But how do i maintain a small subset of tests for browser compatibility. I mean what functions do i've to write in specific for browser compatibility. <HR></BLOCKQUOTE>