About me

Thursday, November 25, 2010

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.

Tip # 3 – Get really comfortable with the application

Since you might not know the languages supported by the web site, it is always a good idea for you to be very conversant with the functionality of the web site. Execute the test cases in the English version of the site a number of times. This will help you find your way easily within the other language version. Otherwise, you might have to keep the English version of the site open in another browser in order to figure out how to proceed in the other language version (and this could slow you down).

Tip # 4 – Start with testing the labels

You could start testing the other language version of the web site by first looking at all the labels. Labels are the more static items in the web site. English labels are usually short and translated labels tend to expand. It is important to spot any issues related to label truncation, overlay on/ under other controls, incorrect word wrapping etc. It is even more important to compare the labels with their translations in the other language.

Tip # 5 – Move on to the other controls

Next, you could move on to checking the other controls for correct translations and any user interface issues. It is important that the web site provides correct error messages in the other language. The test should include generating all the error messages. Usually for any text that is not translated, three possibilities exist. The text will be missing or its English equivalent will be present or you will see junk characters in its place.

Tip # 6 – Do test the data

Usually, multi-lingual web sites store the data in the UTF-8 Unicode encoding format. To check the character encoding for your website in mozilla: go to View -> Character Encoding and in IE go to View -> Encoding. Data in different languages can be easily represented in this format. Make sure to check the input data. It should be possible to enter data in the other language in the web site. The data displayed by the web site should be correct. The output data should be compared with its translation.

Tip # 7 – Be aware of cultural issues

A challenge in testing multi-lingual web sites is that each language might be meant for users from a particular culture. Many things such as preferred (and not preferred) colors, text direction (this can be left to right, right to left or top to bottom), format of salutations and addresses, measures, currency etc. are different in different cultures. Not only should the other language version of the web site provide correct translations, other elements of the user interface e.g. text direction, currency symbol, date format etc. should also be correct.

As you might have gathered from the tips given above, using the correct test environment and acquiring correct translations is critical in performing a successful test of other language versions of a web site.


Look at the tips for testing the web pages which are multi-lingual


Monday, October 25, 2010

How actually it happens............................?

While working on the computer, u get many questions in your mind like.....

How screensaver works?
How Computer hardware works?
How authentication is done?

For such type of questions just get into http://electronics.howstuffworks.com/tech
i'm sure u gonna thank me for this info

Want to know about extensions

Just go to this site

Friday, March 5, 2010

Software Test cycle

Requirements analysis
Checking for the number of Modules in the requirement document
Preparing requirement traceability matrix and checking for the sufficiency of the requirements
Gather the doubts about the requirements from the document and getting them clarified from the client
Test plan preparation
Preparation of functional test requirements
Dividing the test requirements into test cases
Checking for the data required for the test case
Classifying the test case into small or medium or complex
Calculation of the time and effort required for the test case
Test effort estimation
Classification of test cases into small, medium and complex
Analyzing the time and effort required based on the type of test case.
Test case preparation
Preparation of test case title, steps to execute, gathering data for the test case if required, expected result and actual result.
Test case execution
Checking if the test environment is perfect by doing smoke test. Then proceeding for the test execution.
If the smoke test is success. Executing the test case as the steps to execute are written.
If the smoke test failed. Reporting the high severity error immediately after thorough checking and proceeding after confirmation received from the client.
Making note of the defects in the defect tracking tool along with the
i. Image if possible
ii. Actual steps executed
iii. Actual result occurred
iv. Data used for testing
v. Number of occurrences of the defect
vi. URL if possible
Defect management
Making note of the number of defects along with URL, environment, date, time, and number of defects and person who produced the defect.
Defects should be reported to the client and should be declared as bug when confirmed as defect.
Provide a severity and priority to the bug and assign it to the correct developer based on client’s instructions.
Try to reproduce the same bug in the next environment based on client’s instructions.
Change the status of the bug accordingly and the person to whom it should be assigned.