About me

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.