:: QC Boss :: Testing, Independent Software Testing, Manual Testing, Website Testing, Functionality Testing, Usability Testing, QC, QA, UAT

Why do we need cross browser testing?

leave a comment »

In olden days, web surfers are restricted to use any one (or) a maximum of two browsers for their web patrol. In the modern era, (i.e.) World Wide Web there are various major browsers available in the market. As a web developer, you cannot restrict net surfers to a particular browser since they may have many browsers in one system. When your webpage renders across multiple browsers there will be innumerous defects found in the webpage, for example if you own a catalog e-website and if any one of the product or content is not displayed or visible to customer, then there are chances that you might lose the customer and business to avoid these circumstances cross browser testing is widely used.

Widely used browsers:
Google Chrome 19.0.1084.56*
Internet Explorer 9, 10*
Firefox 13.0.1*
Safari 5.1.7*
Opera 12.00*
*version as of June 26, 2012

While using the above browsers the outlook and performance of the websites varies from browser to browser in terms of effectiveness. So it is really essential that your website has to be appropriate with all the browsers, especially for those people who have a big share in the market.

Cross Browser Testing has almost become mandatory for web developers. Adding to it, cross browser testing helps to formulate some of your codes (HTML, CSS, Javascript, JQuery, etc.) are backwards compatible. So when you develop your site it needs to be checked across various browsers, so that all the major functionality gives you accurate results in different browsers. Therefore due to the evolution of various browsers, an increasing demand for various tools for cross browser compatibility came into existence.

Advertisements

Written by QCBoss

June 28, 2012 at 7:40 am

Posted in QC, Website Testing

Tagged with

Organizing a Cross Browser Testing

leave a comment »

A cross browser-testing checklist that can be referred while testing a web project on different browsers and operating systems is referred:

CSS validation
HTML or XHTML validation
Page validations with and without JavaScript enabled
Ajax and J Query functionality
Font size validation
Page layout in different resolutions
All images and alignment
Header and footer sections
Page content alignment to center, LHS or RHS
Page styles
Date formats

Cross browser testing involves testing of web sites or applications on both the sides i.e., client side and server side.

Written by QCBoss

April 5, 2012 at 7:07 am

Cross Browser Testing

leave a comment »

What is Cross-browser Testing

Cross-browser refers to the ability for a website, web application, HTML construct or client-side script to function correctly across all, or the majority of web browsers.

Web Statistics and Trends – Source from www.w3schools.com

2012 Internet Explorer Fire fox Chrome Safari Opera
February 19.5 % 36.6 % 36.3 % 4.5 % 2.3 %
January 20.1 % 37.1 % 35.3 % 4.3 % 2.4 %

Written by QCBoss

March 22, 2012 at 7:10 am

Browser Comparitability

leave a comment »

What is cross browser testing

Cross Browser Testing is a process to check how our web site or application performs on the different browsers, whether the available functions are working properly or not.

What is client side cross browser testing

Client Side Cross Browser Testing is a process to help you to test the functionality of our web application in client side with different Web Browsers.

With the help of Automation tool we can run the client machine in our environment. So that we can run our application with the different browsers.

Once the internal testing is done. Then we go for client side cross browser testing for their satisfaction. The process are follows:

1. To get the client IP address with their permission.

2. Start the Automation tool and type IP address to connect the client machine.

3. Now, we can run the application in our environment with client machine.

4. Finally, Analyzing the report.

What is server side cross browser testing

server side cross browser testing is a process to check the behavior of our web site or application is accessed fromdifferent web browsers.

Written by QCBoss

March 16, 2012 at 10:22 am

Cross Browser Testing

leave a comment »

what is cross browser testing

Cross Browser Testing is a process to check how our web site or application performs on the different browsers, whether the available functions are working properly or not.

What is client side cross browser testing

Client Side Cross Browser Testing is a process to help you to test the functionality of our web application in client side with different Web Browsers.

With the help of Automation tool we can run the client machine in our environment. So that we can run our application with the different browsers.

Once the internal testing is done. Then we go for client side cross browser testing for their satisfication. The process are follows,

 

1.To get the client IP address with their permission.

2.Start the Automation tool and type IP address to connect the client machine.

3.Now, we can run the application in our environment with client machine.

4.Finally, Analysis the report.

What is server side cross browser testing?

server side cross browser testing is a process to check the behavior of our web site or application is accessed from different web browsers.

Written by QCBoss

March 16, 2012 at 9:57 am

Posted in Software Testing

SEO Tips & Tricks for flash websites

leave a comment »

Usage of text in HTML

If you have only a very small amount of text in your Flash animation is to place that text in the <title> tag of the HTML page. Search engines weight page titles high.

Another solution is to put all the text “below the fold” so that although it is contained in the HTML page, the initial experience of visiting your page will be the effect of a bare page containing just the Flash animation.

If your site requires whole paragraphs of text, it is better to place it in the HTML, both from a search engine perspective and a user experience perspective. Keeping text in the HTML makes it easier for search engines to find the text and make sense of it. It also makes it easier for users to search through the text within the browser, print it, or copy and paste it.

Usage of links in HTML

Flash can be a great way to present complex navigation options to users using drop-down menus or other innovative controls. However, it can be difficult for web crawlers to find links when they are embedded only within the Flash animation. Simple solution to this is to make sure that any Flash navigation also appears somewhere on the page as links within the HTML. This can be done easily by putting links at the bottom or left side of a page. These standard practices are also helpful to the human visitors to your site, not just for search engine robots.

Provide a site index page your home page links to – This helps search engines navigate your site—whether or not you make heavy use of Flash. By doing so, human visitors can sense the layout and content of your site easily and web spiders definitely have an easier time hitting all the pages.

Another way to make sure search engines find all the pages in your site is to submit the page URLs directly to the search engines.

Use the Title and Description fields in Flash 8

The SWF file format in Flash 8 supports XMP metadata. The goal of this feature is to help address issues with search engine support for Flash. With this new feature, metadata can actually be output to any version of SWF, not just that generated by Flash 8. It is also a good idea to put this kind of information in your HTML, either in your page’s title and description metadata or in text within the page.

Use separate SWF files onto different web pages

Some websites built entirely in Flash use a single web page with a Flash animation embedded within it. When users interact with the site, new views are displayed within the Flash animation rather than by loading a new, discrete web page.

Although this can provide a great user experience visually and cause faster “page” loads, it has its drawbacks. For human visitors, it is impossible to bookmark a particular page because going back to that same link will take them to the beginning of the Flash experience. Similarly, it is impossible for search engines to understand each new state in the Flash experience as a different page and to link into that state.

Written by QCBoss

August 30, 2011 at 11:09 am

Mobile Application Testing-Automation tools

leave a comment »

          The mobile applications market experiences a drastic demand along with the growing technology in innovative world. So, every mobile application developed should be tested to make sure that it is bug free. Testing a mobile application will be done manually or by using automation tools similar to that of computer applications.

           Along with Manual Mobile Testing, presently many Mobile Automation Testing tools are evolving into the market. Some of the automation tools available to test Mobile Apps are provided below:

Robotium (Android): It helps to create powerful and robust automatic black-box test cases for Android applications.

W3C mobileOK Checker: It determines level of mobile-friendliness by performing various tests on a Web Page.

FoneMonkey (iPhone): This tool records all actions with the iPhone or iPad (while in use) and plays them back as a test script at any time. Through this, we can create, edit and playback the automation scripts that exercise an application’s user interface.

Eggplant (iPhone): It is a GUI automation testing tool for iPhone from TestPlant. It uses Image-Matching technology to test Graphical User Interface.

M-Eux: It allows us to automate, maintain and monitor the mobile test cases. It also identifies the GUI elements of the mobile device.

TestQuest Countdown: TestQuest Countdown consists of consists of 4 components like TestDesigner, TestManager, TestRunner and AssetManager used to develop, queue, run and share respectively.

Sikuli: IT uses visual technology to automate and test Graphical User Interfaces. It uses Sikuli Script, a visual scripting API for Jython, and Sikuli IDE, an integrated development environment for writing visual scripts with screenshots easily.

Deviceanywhere: It is used to test and monitor the functionality, usability, performance and availability of mobile apps and websites.

IBM Rational Performance Tester (RPT): It is an automated performance testing tool from IBM. Through this, a user can create tests, which transacts between an application client and server. During execution, it simulates a large transaction load on the server and collects server response times to identify the application bottlenecks.

Keynote MITE (Mobile Interactive Testing Environment): Using MITE, we can perform activities like:

  • Browse – It enables us to interact and analyze the performance of the real time Web page.
  • Verify – It will compare many aspects of the website against best practices and provide a comprehensive score for each page.
  • Record – The mobile device simulator let us record scripts for all the actions performing while interacting with the website on the mobile device.
  • Run – It runs the recorder scripts on any mobile device.
  • Matrix Test – It automates testing by running one or more scripts on multiple devices concurrently.