can anyone help me how can I test the browser compatibility of my web site.what are the tools that can help my work done.And how can I check for the compatibility using those tools.
can I check the browser compatibility using winrunner???
Please help me.
ALWAYS CURIOUS TO LEAN NEW TECHNOLOGIES--------------------Radhika
[This message has been edited by lradhika (edited 11-03-2001).]
I have done quite a bit of web application testing user both Segue SilkTest and Mercury WinRunner. Neither can be used to create tests which are cross-browser compatible without some runtime coding efforts. Depending on the web application under test these changes run from minor to substantial.
I have found that the cross browser compatibility issues come in two classes:
1. The dialogs and logic associated for performing some tasks are different enough that you need to record individual GUI declarations [SilkTest] or GUI Map objects [WinRunner] along with separate functions for each browser. An example of this class of problem is interacting with IE and Netscape to save a file [make sure you consider what happens if the file exists or the directory is non-existant]. While this work is subtantial it is predictible ahead of time--and the work can be reused in other testcases and test suites.
2. Objects are seen differently by the tool for each type of browser. This type of problem in not predictible until you have the application running in both browsers. Failures are easy to find [i.e. the test stops at each unknown object]--accomodating the differences can be minor [i.e. a GUI declaration/Map change] to significant [runtime IF/ELSE statement(s)]. This class of cross browser problems are very time consuming if you have hundreds/thousands of lines of code.
My strategy now to deal with cross browser compatiblity testing is:
1. Pick the browser most often used by the application's users [tough call I know] and target that browser for all automated tests.
2. Only expend the effort of cross browser script modifications for smoke tests (sometimes referred to as basic acceptance tests).
3. If some of the testing is done manually then ensure that all of that testing is done with the other browser [i.e. the one not used in step #1 above].
While this strategy entails some risk, the risk of new tests not developed because of the time spent modifying an automated test so it is cross browser compatible is certainly greater.
-Hope this helps, Terry Horwath
[This message has been edited by Terry Horwath (edited 11-05-2001).]