sankar.raparthi

 Profile Answers by sankar.raparthi 

• Aug 22nd, 2008

 

There are lot of issues which may arise while Testing in Two or more browsers.

Eg.: Following are some points while comparing IE with Mozilla, in IE following issues may occur which needs Compatability testing but does not occur in Mozilla

1. Java Script errors.
2. DIV Tag issue.
3. GetElementBy Issue.
4. Parent and Client Window size, pixel related issues may come.
5. After JS in IE sometimes it may not take us to further navigations.

npinnamaneni

 Profile Answers by npinnamaneni 

• Sep 12th, 2008

 

We can easily identify Java Script Errors in mozilla when compared to IE Browsers

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Mar 9th, 2009

 

Hi

I can execute the cases for below ones.

-> Usability cases ie align ments, fong sizes and place of the controls
-> Invoking and closing of Child windows
-> Browser close buttons in child windows
-> Opening a new window from main window
-> java script errors
-> Checking Hiding controls
-> Checking the tool tips of the controls and help text


Srinivas

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Mar 9th, 2009

 

I will write Test cases Combatable for different browsers with differnt version . main thing to point out is..

1) Controls(Buttons,Drop down box, Pop-down menus, Popup menus).
For buttons some times the click action supports for one browser(IE7.0) and it will not work in Mozilla browser(3.0.6). i faced this in my real work projects. In some cases the Popup menus overlapped, hidden by other controls, which makes inact state, In Drop down box lengthy items supported by one browser and another didnot , which make break down in text)

2) GUI Check: Check the Graphical interface in the project supports for differrent browsers and components.

3)Interfaces: Ensure that all the links are working fine and should open correct pages.

4)Design issues- Desgin patterns are varied according to different CSS files, which afftects the design of the pages for different browsers.

The system is said to be compatible which not only support for different browsers, it shoul support for diferrent Operating System & other Hardware Components. My Testcases should covered by those 4points

ashishks

 Profile Answers by ashishks 

• Aug 25th, 2009

 

We should execute all test cases in different browsers like IE 7.0,8.0, Firefox 3.0,3.1 and Safari 3.1,3.2. Also we have to excute all test cases in different operating systems like XP 2000, XP Vista and Macintosh.

If we have to perform compatibility testing then at least each test case should be executed in different environments.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Jan 1st, 2010

 

Compatibility testing is performed on an application to evaluate how it performs in different computing environments. A computing environment contains any number of the following components:

1) Operating systems (Windows, Mac, UNIX, etc.)
2) Browsers (Internet Explorer, Firefox, Netscape, etc.)
3) Compatibility of peripherals (printer, disc drive, etc.)
4) Database (SQL, Oracle, etc.)
5) Computing capacity of hardware platform (IBM 360, HP 9000, etc.)..
6) Bandwidth handling capacity of networking hardware
7) Other System Software (web server, networking/ messaging tool, etc.)

Web browser compatibility testing considers the following things:

1) Funtionality
Validate the application does what it is supposed to do across selected browsers

- mandatory and optional input
- paths that have hidden fields or text
- validation messages
- error messages

2) GUI
The following page elements should conform to specifications across selected browsers

- positions of frames, tables
- initial focus
- focus leaving and returning to pages
- tab order
- text appearance
- headings, titles, and labels
- text boxes
- validation
- menus and lists
- internal links  
- external links   
- email links  
- there should be no orphaned or broken links
- graphics, images, and multimedia
- advertisements
- navigation
- scrolling and paging
 

3) Usability

4) Performance

5) Concurrency

6) Localization

7) Accessibility