About me

Thursday, November 17, 2011

Browser Compatibility testing OR Cross Browser testing

Browser compatibility testing which is also called as cross browser testing, multi browser testing , in simple words, is testing a application in different browsers and also in different versions of browsers. This task is mostly automated because it is very difficult to perform it manually. But here I’m going to provide a series of steps which will help you give more test coverage by performing the cross browser testing manually. At the same time there are many hurdles when you start testing a application in different browsers. For example chrome will not let you install different versions of it in your system, similarly with Firefox. So here we go for a quick round up of how to test a web application in different browsers with different versions without struggling.

Points to be remembered before performing such testing
  1. Note down all the browsers along with their versions in which application needs to be tested. Check the minor versions in them and reduce the count by removing minor versions. For suppose if Firefox version 3.5 and Firefox 4.0 does not have any major changes then select any one of them. Reducing the number of browsers will reduce lot of effort.
  2. Consider these scenarios as part of your basic test plan
    1. Test major css (cascading style sheet) issues
    2. Check for end to end flow
    3. Check the user interface issues
    4. Display of controls, pop ups, flash images. Alignment of the controls also. Font size font color.
    5. JavaScript features
    6. Performance or page load time
    7. Browsers with different screen resolutions
    8. Html validation
  3. If a tool is to be selected for cross browser testing, then check following factors in the tool.
    1. Is it an open source?
    2. Does it provide different versions of at least popularly used browsers Internet Explorer, Mozilla Firefox and Google Chrome?
    3. Does it provide screenshot for the URL which we provide? Or does it let us navigate through different links in the application?
    4. Please check “Best articles on Cross Browser Testing” section at the end of this post for the list of tools which does cross browser testing and also main features of each tool.
Cross browser testing Automated

Tuesday, September 27, 2011

Scrum Methodology - Quick Info

It is one of the unique methodologies of agile methodology.


It is an iterative, incremental framework for project management. It is a loose set of guidelines that govern the development process of a product, from its design stages to its completion. It aims to cure some common failures of the typical development process like a. chaos due to changing requirements, unrealistic estimates of time, cost and quality of the product.


1.     Daily Scrum meeting or daily stand up meeting: agenda:  what is done, what is planned for today, what are the problems in accomplishing the goal?
2.     Sprint planning meeting : Before each sprint cycle (7-30 days)starts, prepare sprint backlog, timelines,
3.     Sprint review meeting: done at the end of sprint cycle, review work completed and not completed, demo the work completed, do not demo incomplete work, 4 hour time will be allocated.
4.     Sprint retrospective meeting: done at the end of the sprint cycle. Questions are asked - what went well during the sprint and what could be improved in the next sprint. Make continuous process improvements

Sprint Burn Down Chart

1.      Depicts the total Sprint Backlog hours remaining per day.
2.      Shows the estimated amount of time to release.
3.      Ideally should burn down to zero to the end of the Sprint.

Scrum roles

1. Product Owner
2. Scrum Team
3. Scrum Master

 Click below for diagrammatic representation of scrum workflow and also for traditional diagram of scrum workflow

Wednesday, August 24, 2011

Input Data Validation

Every web application is expected have at least one submit form. Data entered in form is transferred as input to database or to any other application and will decide the output. So, input data plays a very important role in retrieving the output data.

Such data needs to be validated by the code. And tester has the responsibility of validating such data.
At this point tester thinks about how can the validations be done and what type of data should be provided to validate the input field. Test data needs to be created and passed to the form through the automation tool or manually.

Here are few steps or guide lines to validate the data.

Let’s consider a sample form which acts as input to signing in as new member in a social networking site like facebook. It contains different types of input fields – Numeric, String, Alpha Numeric, date, preset values (from drop downs or check boxes), file uploads and Email addresses.

Name: String input field
Password : Alphanumeric field
Age: Numeric input field
Address: Alpha numeric
Date: Date of Birth
Email Address: Email field
Profile Image: Photo of the member: File upload

Validations which can be performed on such forms are

1.      Name :
a.       Should start with letter
b.      Should not contain numbers.(unless proposed)
c.       Should contain string characters only.
d.      Can contain underscore (_) ,hyphen  (-) and single quotation (')
e.      Can contain space but along with string characters
2.      Password :
a.       Should be encrypted with any special character and should not be visible even to the person who is entering it. Generally it gets skipped from encrypting when it is passed through any testing tool.
b.      Can contain string characters, numerical and special characters.
c.       Should not contain only spaces
d.      Length factor should be tested.
3.      Age :
a.       Should start with number
b.      Should not contain characters
c.      Should contain numbers only
d.      Should not contain special characters and spaces also
e.      Should not have all zeroes or single 0
4.      Address :
a.       Can contain string characters, numeric, special characters.
b.      Should contain only spaces
c.       Should not contain junk data, it should be meaningful
5.      Date :
a.       Can contain numbers
b.      Can contain special characters like hyphen (-),slash(/) depending on format accepted
c.        Can contain string characters depending on format
d.      Some cases should not accept future date like for date of birth we cannot put future date.
e.      Some cases should not accept past date like for any activity which is planned for future date.
6.      Email Address :
a.       Can contain numeric, string and special characters
b.      Should not contain only special characters or numbers
c.       Should not contain only spaces
d.      Should contain at least one at symbol (@)
e.      Should contain at least one dot (.)
7.      Profile image :
a.       Should be a path to the file which is to be uploaded
b.      File should be existing
c.       File format should be acceptable with the input field
d.      File size should be in the limits mentioned
8.      Apart from above we should also check the following in the input provided
a.       Length acceptable in the field
b.      Minimum length criteria is accepted or not
c.       Is the field mandatory ---then input is must and no spaces and all zeroes should be accepted.
d.      More number of spaces provided at the end or in between or at start of the data should be trimmed.
e.      Data in the form of SQL queries should not be accepted as they are provided to break the security system by hackers.
f.        Date which has HTML tags should not be provided. As they might be interpreted in different form when submitted as input data.

Points to be noted by developer when submit forms are designed

1.       Highlight the mandatory fields either by asterisk (*) or text “Mandatory” or coloring the text box in differentiating color.
2.       Mention the acceptable format near the date field.
3.       Mention the max length for the input fields which has limit restrictions.
4.       SQL queries should be identified and rejected.
5.       Same with HTML tags, they should be identified before passing the data.
6.       Errors should be in red. Or fields which have incorrect data should be highlighted in red.
7.       Provide the error message near each error field. Or provide all the errors in one section of the page mentioning the data field names clearly.

Tuesday, August 23, 2011

Bloggers day

Lets celebrate Bloggers day on August 31st.

Get ready with the 5 new blogs which you like to recommend to others.

Why is August 31st selected as bloggers day?

August 31st means '3108' which resembles 'Blog'.

For more details of it visit the site http://www.blogday.org/

Thursday, July 28, 2011

Test More n more

Testing it is just not a word but it is that act which gives value to the product developed by the developers. It is given more significance in present days but that value needs to be enhanced. Why, let’s see few examples of apps which were not tested perfectly and are in market with defect.
These points are based on an excellent article “Perhaps they should have tested more” presented by Joe in his blog. Thanks Joe.
1.    Apple Iphones: Have IPhones failed to make the Daylight Saving Time transition yet again?  iOS 4.1 users in Europe reported that their alarm clocks failed to account for the time change due to the end of Daylight Savings, which shifted their clocks back an hour at 2 am this morning. As a result, their alarms went off an hour too late.
2.    Skype: Supernodes not so super? Skype once again had a worldwide outage related to software problems in their supernodes
3.    Google Docs: A recently-introduced bug in Google Docs caused some documents to be shared with users who were specifically not authorized to see them.
4.    Microsoft Zune : Zune 30s all freezing up at once
5.    Target: National retailer Target Corp. has been shortchanging customers for months when they use some manufacturers' coupons.
6.    JP Morgan Chase : Millions of customers who bank online with J.P. Morgan Chase & Co. lost electronic access to their accounts as the company's website suffered a severe outage starting Monday at 11:00 PM ET.
7.    Apple iPhone4: Recently, Apple iPhone 4 users have been complaining about poor reception when the phone was held certain ways. Without debating if the diminished reception is real or not, Apple has now figured out that the algorithm for calculating the number of bars to display has been wrong for a long time!
8.    Google Android: Who knew that simply texting the word "reboot" would actually cause a phone to reboot?
9.    Apple: A critical bug in Apple's Snow Leopard OSX 10.6 reportedly can wipe out users' account information when they open and close "guest" accounts.
10. McAfee: Due to a faulty virus definition update, machines running Windows XP Service Pack 3 using the faulty definitions will delete svchost.exe, causing many key Windows services to fail to start. This Windows file is being mistakenly detected as W32/wecorl.a. Failure to start svchost.exe causes Windows to automatically reboot.
11. 6Pm.com: 6pm.com, the sister site of Zappos, messed up the coding of business rules in their pricing engine, resulting in undercharging customers to the tune of approximately $1.6 Million.
12. StarBucks: For a couple of days in May, coffee giant Starbucks ended up double charging about 1 million of their U.S. and Canadian customers. 
13. TESCO: Giant UK supermarket chain Tesco has been unable to take money at a number of its stores following technical problems affecting its tills.
14. Manitoba Public Insurance: Everyone knows that a typo is a low-severity, low-priority bug, right?
Well as Manitoba Public Insurance learned, sometimes a typo which slips through into production can be a rather expensive proposition - both monetarily, and politically as well.
15. Zecco: On April 1, 2009, online brokerage site Zecco increased about 1% of their customers' Buying Power balances by millions of dollars. Some customers thought it was an April fool’s joke.  The real reason wasn't quite as funny.
16. Skynet: It's no surprise that self-aware systems will always turn on their creators - anyone could see that coming.  But buggy robots?  There's just no excuse. A robot forgets who she is.
17. DropBox: During a recent code push, web-based file storage firm Dropbox introduced a bug in their authentication mechanism - allowing unprotected access to accounts for four hours.
18. Netflix: Still waiting for your copy of Rambo, 27 Dresses, or The Bucket List to arrive from Netflix?  You may be waiting a while, and you may not be alone.

Wednesday, June 15, 2011

Google search can now search for snapshot

New feature of snapshot search is coming up in Google search. See this link

Check for the camera icon in Google search page, which indicates that this feature is available for use.
Waiting for the plug-in to be available.

Monday, May 30, 2011

Do you know which is the first bug found

The invention of the term "bug" is often erroneously attributed to Grace Hopper, who publicized the cause of a malfunction in an early electromechanical computer. 

A typical version of the story is given by this quote:
In 1946, when Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark-II and Mark-III (The Harvard Mark II was an electromechanical computer built at Harvard University under the direction of Howard and was finished in 1947. It was financed by the United States navy). Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug. This bug was carefully removed and taped to the log book. Stemming from the first bug, today we call errors or glitch's in a program a bug.
Hopper was not actually the one who found the insect, as she readily acknowledged. The date in the log book was 9 September 1947, although sometimes erroneously reported as 1945. The operators who did find it, including William "Bill" Burke, later of the Naval Weapons Laboratory, Dahlgren, Virginia were familiar with the engineering term and, amused, kept the insect with the notation "First actual case of bug being found." Hopper loved to recount the story. This log book is on display in the Smithsonian National Museum of American History, complete with moth attached.
While it is certain that the Harvard Mark II operators did not coin the term "bug", it has been suggested that they did coin the related term, "debug”. Even this is unlikely, since the Oxford English Dictionary entry for "debug" contains a use of "debugging" in the context of air-plane engines in 1945.

See the first bug picture 

Thursday, April 28, 2011

CMMi and TMMi

Many heard about CMMI (Capability Maturity Model Integration)

But that subsets all points of development and testing. Focus is more on development rather than quality activities. What about the quality which actually adds value to the project.

Here comes TMMi (Test Maturity Model Integration)

Quality and testing which is given low preference sometimes than development, needs a change. And here is this foundation which actually created TMMi and I guess IT industries need to start creating a space for TMMI along with CMMi.

Please check the site of TMMi foundation here

To know its impact read these articles

Tuesday, April 12, 2011

Strip off Html tags from excel

When data is exported from any web page into excel or from any other sources into excel. It gets copied with html tags. This is making it difficult to read it. If there are few rows then we can remove them manually but if we there are more number of rows then we can go for below steps.

Follow these steps:

1.    Open up the VBE with Alt+F11.
2.    Locate your workbook in the top left Project Explorer window. Right-click on your workbook and choose Insert>Module.
3.    Paste the below given code in to the code module that will open.
4.    Go back to Excel, select the cells you want to clean and activate the macro with Tools>Macro>Macros. (Macro can also be activated by clicking Run icon in Visual Basic).
5.    All the html tags will be replaced.
6.    But sometimes some cells will be displayed as hashes. In such cases, select the Description column again and select Home > Clear > Clear Formats. This will get back your description.

Tuesday, April 5, 2011

How to test search functionality

Every web application by default will contain search feature in it. Many search engines’ main functionality is search feature.
The parameters to be considered while developing this feature or testing this feature are not limited. There are many factors which should be looked in when checking the coverage and usability of the search text box in the application.
Preparation before testing the search functionality
1.       Note down the valid input details for the search feature.
2.       Find out the minimum and maximum range.
3.       Find out the depth of the search – document search, word in a document, image search
4.       Should document search display the size of the document also? Similarly for image?
5.       Any advanced search features like document or image type selection to refine the search are available?
6.       General set of input which can be given are
a.       A-Z
b.      a-z
c.       0-9
d.      {      [              (              ~             !              @            #             $              %            ^             &             *             `               |        \              :               ”              ;               ’               <             >             ?              ,               .               /              *             -        +             )              ]              }
e.      Blank spaces

Work with these inputs when testing the search functionality

Wednesday, March 23, 2011

Estimation of the test effort

Estimation is the base step of any project. If it is not strong then the whole project and sometimes the client itself will be out of our hands.
It is not an easy task and not a difficult one too. Not every estimation is successful. Too much of estimation will lose the client and less estimation will scare the employee.
Balancing both and winning the project is what needs to be learned.

Here are the factors which should be considered before making estimation
1.       Technical
a.       Experience and Knowledge of test team in the technology which is used.
b.      Type of application – web application, executable file, games or any other.
c.       Technical dependencies (if development and testing team is not at one location).
d.      Tools used and their flexibility
2.       Functional
a.       Number of requirements free zed
b.      Number of critical functionalities
c.       Types of testing done – User interface testing, cross browser testing, localization testing and many more.
3.       Project level dependencies
a.       Project Scope
b.      Project methodology – Agile or Scrum
c.       Estimation model used
d.      Experience in previous project similar to this
e.      “Fixed cost” and “Time and Material” project
f.         Team size

Example estimation for a web application 

Thursday, March 17, 2011

Want to spell check and grammar check your complete web application

Excellent tool to check spelling errors, grammar and broken links in complete web application.
If you want to crawl the entire web application and check for spelling mistakes, typo errors you  do not need to check each page manually. Let your application be multi-lingual web application, but it can check for the spellings.

Here is a super tool for it     Inspyder Software

Features at its best –

  1.        Check the spellings of the complete web application
  2.           Check the grammar mistakes of the complete web application
  3.           Check for the broken links
  4.           Lets you select any language as the dictionary against which spellings are compared.
  5.           Provides you to create a custom dictionary which contains a set of words which are not actually spelling mistakes in your application.
  6.           Provides good report based on your preferences.

Check the site http://www.inspyder.com for more features and tools of it.

Tips for testing multi-lingual web sites

This is a article by: Inder P Singh(picked from a site)

These days a number of web sites are deployed in multiple languages. As companies perform more and more business in other countries, the number of such global multi-lingual web applications will continue to increase.

Testing web sites supporting multiple languages has its own fair share of challenges. In this article, I will share seven tips with you that will enable you to test the multi-lingual browser-based applications in a complete way:

Tip # 1 – Prepare and use the required test environment
If a web site is hosted in English and Japanese languages, it is not enough to simply change the default browser language and perform identical tests in both the languages. Depending on its implementation, a web site may figure out the correct language for its interface from the browser language setting, the regional and language settings of the machine, a configuration in the web application or other factors. Therefore, in order to perform a realistic test, it is imperative that the web site be tested from two machines – one with the English operating system and one with the Japanese operating system. You might want to keep the default settings on each machine since many users do not change the default settings on their machines.

Tip # 2 – Acquire correct translations
A native speaker of the language, belonging to the same region as the users, is usually the best resource to provide translations that are accurate in both meaning as well as context. If such a person is not available to provide you the translations of the text, you might have to depend on automated web translations available on web sites like wordreference.com and dictionary.com. It is a good idea to compare automated translations from multiple sources before using them in the test.

Tuesday, March 8, 2011

IE6 countdown started

Many do not like using IE6, for such there is a news

IE6 countdown is coming to 1% from 6%.

Do your bit by joining the cause in http://www.theie6countdown.com

You also have a new and a great looking IE9 released. Enjoy working on it.

Tuesday, March 1, 2011

Extract all URLs in a web page

Excellent way of extracting all URLs from a web page.
If you have a web page and you want to extract the URLs in complete web application, there is a way.
Go to http://www.web-max.ca/PHP/misc_23.php, enter the URL in the text box given at the end of the php code.
It crawls the entire web page and extracts all the URLs in the web pages and provides the list.
Copy and paste it in the excel.
Thanks for the Cool code.

Factors for link testing

Link testing
Many feel its just clicking the links, but it is not so. It has many factors which are supposed to be checked when testing the links in any web application.

Factors for link testing

1. Check the link style- color,font,color when already visited
2. Check the tool tip for the link
3. Check the navigation of the link
- Navigating to a web page in same window
- Navigating to a web page in different window
- Opening a document in same page
- Opening a document in different window
- opening an image or video
4. Check the parameters saved in cookie if the application is localized
5. Any identification if it is an external link.
6. Performance of the link
7. Time taken for navigation of the link

There are many tools or link checkers which navigate through the complete web application and provide the list of breaking URLs.

I suggest Xenu link checker.

Observe these key factors when using link checker for testing links

1. Link checkers can take web page as input and local files also as input
2. When testing the links online, check if the link checker will crawl the complete web application or just consider the main page only.
3. What are the types of input the link checker can take - web page,excel
4. Does it have the option of excluding the external links
5. What types of output does it generate? - Excel,html file or any other
6. Does it provide the performance issues and time out issues also.

Monday, February 21, 2011

Google helps you search and receive search results through email

To search and receive google search results through email. Just send an email to google@capeclear.com and enter the text of your query in the "Subject" line. You will receive the search results as email to your mail id.

Once you get the result for the searches... u can get the contents of a URL using the below feature!! To receive the web content of a url send email to web@pagegetter.com and subject should contain the URL whose content has to be fetched.
Thanks to the No-Internet and only MAILING community.

Friday, February 18, 2011

Check external links in excel

I thought
Testing or checking the hyperlinks which are navigating to external web page is a tedious task.

Searched for a tool very seriously which can test all the hyperlinks in excel and produce a report of the broken links.

Did not found any tool which can take excel with hyperlinks as the input and produce report.

Requirement was - An excel is available with many hyperlinks. I need to check each link and prepare a report of which one is working and which one is not working.

Finally got a solution

1. Copy only links from the excel which are to be tested to new excel sheet.
2. New excel sheet should not have any labels or any cells containing values other than hyperlinks type.
3. Save the excel as web page.
4. It will be saved as .html page.
5. Input this html page to any link checker which takes the web page as input.
6. See that "checking local links" option is set in the link checker.
7. This HTML page should be given as a file input to link checker rather than giving it with http protocol.
8. Obviously you will get the report from the link checker.
9. If the link checker has the option to save the report in excel then its good and best for you.