Skip to main content

HOW TO PERFORM COMPATIBILITY TESTING!!!



In a previous post, we have discussed what is browser compatibility testing. And in this post, we are going to discuss that how can we perform compatibility testing. Before discussing further, Let us first revise a bit about compatibility testing.
Browser compatibility testing simply means testing your website or application on different browsers. Compatibility testing also called cross-browser testing.


BROWSER COMPATIBILITY TESTING IS PERFORMED BY

It is tester's responsibility to determine that which browser should be chosen as there are millions of browser present.
Other personalities like the client, business analysis, and marketing team also take a healthy competition.
Sometimes companies also keep in mind that which browser is mostly used or you can say which browser attract more traffic and then the browser is chosen accordingly.

Whoever performs compatibility or cross-browser testing, but final results are thoroughly examined by design and development team and relevant changes are performed by them only.

HOW BROWSER COMPATIBILITY TESTING IS PERFORMED????
Like all another testing, browser compatibility testing is also performed in various systematic ways or steps. Let's discuss in case of compatibility testing what these steps are:
The first thing to think about browser compatibility testing is whether that browser compatibility testing is done manually or by using tools?
So the answer to this question is that cross-browser testing can be done manually, But as due to the involvement of multiple browsers, multiple system, and multiple operating systems, many problems occur so in order to cope up with this complex situation we are provided with various related tools in order to make our work easier and more efficient.

  • As discussed earlier, traffic scenarios are considered to judge which browser should be tested
  • Sometimes tester often confuses that what part of AUT(Application under test) is to be tested or if all of it at once, but I should tell you that the basic strategy, in this case, is to test 100% features of AUT on one platform or browser and on remaining platforms just check the vital feature or functionality
  • After determine that what feature of AUT is to be tested on which browser, the testing team aims to discuss various other things like risk, time and cost, which sort of people to be included, issue tracking schedules etc.
  • The fourth step in browser compatibility testing is to write various test cases in order to a validate the efficiency of the system.    
  • After validating or executing various test cases. Testing team pass on the results to the develop/design team.
After discussing HOW BROWSER COMPATIBILITY TESTING IS PERFORMED, Let's discuss WHERE AND WHEN IT SHOULD BE PERFORMED FOR BETTER RESULTS.
WHEN
  • In order to manage cost and time, Compatibility testing should also be started in initial stages.
WHERE
  • Cross browser testing is performed on one of the following:
  1. Dev
  2. Production environment 
  3. QA
                   

Comments

Popular posts from this blog

Steps To Hunt the Bugs Successfully

The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...

Cross browser testing Tools

Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...

Mobile Application Testing: Strategy for Development

There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...