Cross Browser Testing---what is it?

Now a days we talk more on browser compatibility. Every Manual Testing is having a mandate part as
Browser Compatibility.Web browser is a translation device. It takes a document written in the HTML language and translates it into a formatted Web page.What happens in HTML. It converts the HTML code to machine language and sends through wire by binary format.The receiving device(mobile and computer) catches the binary code and converts that code to HTMl. After that it shows to the user.

Let me jump into the problem.Very few people code HTML by hand anymore. There are a multiplicity of programs such as DreamWeaver and Microsoft Front Page which help make the process of web page creation easier.The basic rules for translating HTML documents are established by the World Wide Web consortium, which publishes the official HTML standards. But there's considerable room for interpretation within those ground rules.

For example, the HTML standards say that the TABLE tag should support a CELLSPACING attribute to
define the space between parts of the table. But standards don't define the default value for that attribute, so unless you explicitly define CELLSPACING when building your page, two browsers may use different amounts of white space in your table.
In addition, the HTML standards usually run ahead of what the browsers support. No browser as yet
supports 100% of the HTML Version 5 standard, but some browsers come closer than others. Over the
past few years Internet Explorer has done a much better job of this than Netscape Navigator, though
Opera has done arguably the best job.But since support for the latest HTML tags isn't universal, you
could be building your pages with parts of the language that not all browsers understand. In that
case the browser will ignore that part of your page it can't translate, and the way your page
displays will be affected.

One of the greatest problems with CSS, or Cascading Style Sheets, is the issue of cross browser compatibility. What may look great in Mozilla browsers looks terrible in Internet Explorer, and may
totally break in Netscape. The biggest mistake a web designer or developer using CSS can make is to
design for only one browser, or to assume that since the largest group of viewers use IE, to disregard its flaws that are apparent in other browsers.

The new cutting edge Ajax technology is also browser dependent.So Browser compatibility testing is must for Ajax based Application.

In the case of business-to-consumer (B2C) style web applications, cross-browser compatibility will
generally be necessary. Customers resent being told which product to use and they may not have disk
space to load a second browser on their hard drive. Also, certain ISPs support only one browser.
If your browser choice conflict with the ISP, you have put your customer in a difficult situation.

In business-to-business (B2B) web application, you may be able to insist that a particular browser
be selected. It will depend on your relationship with the counter-parties, standards in that industry and the number of counter-parties involved.
The cross browser problem is getting complicated by browser-specific "HTML extensions." Back during
the heyday of the Browser Wars, both Netscape and Microsoft tried to get a competitive edge by
running ahead of the HTML standards, inventing their own tags and attributes.Those are basically
custom tags and attributes only viewed in the compatible browser only.

So Browser Compatibility or cross browser testing is a technique by which we can test a webpage in different browser and check the itegrity of the page.
Cross Browser Testing---what is it? Cross Browser Testing---what is it? Reviewed by Animesh Chatterjee on November 18, 2009 Rating: 5

1 comment:

  1. Hi Animesh,

    Your blog askQTP is a great resource for many. We liked your blog a lot. Keep it up.

    iAsk. iAnswer.


Powered by Blogger.