7 Basic Tips for Testing Multi-Lingual Websites

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

Testing Websites supporting multiple languages has its own fair share of challenges in today's world. 

Tips for Testing Multi lingual websites

In this article, I will share seven basic tips which will enable you to test the multi-lingual browser-based applications in a complete way.

Basic Tips To Test The Multi-Lingual Browser-Based Applications

Tip #1: Prepare And Use The Required Test Environment

If a website is hosted both in English and Japanese languages, it is not just enough to simply change the default browser language and perform identical tests in both the languages.

Depending on its implementation, the website 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 website is to be tested from two machines – one with the English operating system and the other 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 the 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 websites like Wordreference.com and Dictionary.com.

It is always better 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 website, it is always better for you to be very conversant with the functionality of the website. Execute the test cases in the English version of the site a number of times. This, in turn, will help you to 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 website by first looking at all the labels. Labels are the more static items on the website. 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 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 website 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 it's English equivalent will be present or you will see junk characters in its place.

Tip #6: Do Test The Data

Usually, multi-lingual websites 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 the data in the other language on the website. The data displayed on the website should be correct. The output data should also be compared with its translation.

Tip #7: Be Aware Of Cultural Issues

A challenge in testing Multi-Lingual websites 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), the format of salutations and addresses, measures, currency, etc. are different in different cultures.

Not only should the other language version of the website provide correct translations, other elements of the user interface For Example, 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 website.

About the Author:

This article is a guest post by Inder P Singh.

It would be interesting to know your experience with Testing Multi-Language websites.

Recommended Reading

68 thoughts on “7 Basic Tips for Testing Multi-Lingual Websites”

  1. Many thanks to this article. This is very useful for me as i am currently testing japanese and simplified chinese application

  2. This is indeed a good article. This article has opened up different possible erroneous areas while testing a Multi-Lingual Web application. Many thanks to this article.

  3. Hi, these multi-lingual web sites tips had been a great help for me as currently I am testing web site which is in English and Japanese language. Testing is in very initial phase and we were struggling to finalise the approach for this testing, this article has been a great help in finalising an approach for my testing.

  4. Thanks for this article , its very useful , i want to know about test cases – how to write test case (GUI, validation, Functionality).

  5. Indeed a nice article,
    Can you please share some knowledge about Multi-institutional supports in testing.


  6. Testing multi language web site is always a fun. I am on project of website internalization and multi language support is part of this project.
    We find testing such application is very challenging and also fun work.
    Besides testing testers can pay little attention over web site design also. Multi lingual web sites have some design standards like defining web page language in the head section
    and converting meta tags to respective languages for SEO.
    As a testers we can test these finer details to make multi language web site a success.

    My wishes for this testing community..

  7. is it similar to WAI(Web Accessibility Initiative)Testing..where we chack across various GUI related Information…
    also those who are perforing this testing can get more information on W3C site..

  8. Hi,

    I am working on a application with 12 different languages.Here we have to select the language from drop down while login to the application.

    But we are using only one machine to test for all langauges.we are not using different operating systems.Does it means it is wrong process?
    we will get the coverted words for different languages from the client.
    we will verify the lables according to the data.

  9. Multi Lingual testing is very visual and can be tiresome on the eyes. The German umlaut and the French accent on the letter ‘e’ were often handled incorrectly and they either caused the application to crash (when the text was part of an error message), or the text that followed the special character would not be displayed at all. I’m now testing an English only accounting and distribution app., with seems to have a language of its own!

  10. hi i am testing multilingual website. it is in initial phase please tell me about more about multilingual website. It is in english wants to convert in french & portugese

  11. hi all, i am Rajesh. i am new to testing. may i know that what is the organizational structure? that means what are the different designations in a company and in testing field, i.e. like project lead, test manager, team lead….etc. plz clarify me.

  12. Its a great article as you have covered each aspect of multi language application testing. These are very useful tips which will surely help me during testing multi language application.

  13. Dear all,

    Many thanks for your comments!


    Please refer the article on writing effective test cases that is available at https://www.softwaretestinghelp.com/how-to-write-effective-test-cases-test-cases-procedures-and-definitions/


    Although a software application with multi-institutional support is naturally more complex than a similar one serving a single customer, their testing is fundamentally not different. However, the following points should be taken care of while testing the former:
    1) The test environment should reflect multiple customers.
    2) Application configuration and customer configuration functionalities should be tested carefully. Customer application functionality will be impacted by both the application configuration as well as customer configuration.
    3) Data of one customer should be secure from the users of another customer.

    Inder P Singh

  14. Rajender,

    Are you working on a Windows based application or a web based application? Please note that a couple of these tips are for web-based applications only.

    It will give you more confidence if you are able to use a test environment that is identical (or as similar as possible) to the one that will be used by the end-user. Therefore, if you are testing in Spanish and have a test machine with Spanish operating system, any problems that you see are likely to be the ones seen by the Spanish user.

    Inder P Singh

  15. Mitrasen,

    Although a software application with multi-institutional support is naturally more complex than a similar one serving a single customer, their testing is fundamentally not different. However, the following points should be taken care of while testing the former:
    1) The test environment should reflect multiple customers.
    2) Application configuration and customer configuration functionalities should be tested carefully. Customer application functionality will be impacted by both the application configuration as well as customer configuration.
    3) Data of one customer should be secure from the users of another customer.

    Inder P Singh

  16. thank you Inder. One issue…
    Points 1 and 3 stated here comes under defn of multi-insti. Its ok !
    Regarding topic 2…while testing application config for a particular institution treats it like single institutional. can you please tell what aspects are practices of testing might be implemented for multi-institutional platforms. For example we are testing a Credit Card application which can be sold to many banks, keeping them on instituition level. We are dealing them separately and no conflicts so for…Is there anything more we need to test ?


  17. hi friends, i am into testing for few months, i have been assigned diffrent web applications to test (only GUI TESTING), I am putting my 100% effort to find each and every bug — but i cant, can any one help me out, what a areas to be concentrated— brief in very detail so i can falloew u

    with regards

  18. Nice points. Some random thoughts from my side on this subject-

    – Sorting is another important areas that should be tested in the International websites. This can be tested in any areas of websites that displays the information in the tabular format. Sorting rules differ from locale to locale are a tricky proposition to test.
    – Again, different countries may have different preferred payment types. If a website support multiple payment types, these should be throughly validated for default payment type in the website.
    – There can be layout issues in the multi-lingual website. Because of string expansion, the text representation in different language wesbites will invariably differ primarily resulting in text truncations
    – For a website being internationalized for the first time, it may be worthwhile exploring the use of Pseudo translation approach at the early stages of testing. It will help to find potential translation and hard coding issues much before actual translation has taken place.
    – If fonts are not extarnalized properly, the different language websites may give text representation issues.
    – After all this, imagine testing a Middle Eastern language- the whole paradigm of UI testing reverses in order to test Right to Left (RTL) UI.
    – The Development guideline at the following URL may give some more ideas to test an International website-


  19. Hi,
    Nice article….Inder
    Write now I am working as a software tester and also learning Japanese. Can any one help me in knowing how to get into the multilingual testing job?


  20. Hi
    Nice Points, Some points from my side.

    -Placeholders ae another very important area to be checked by placeholders i mean the labels, some dynamic content on the header image and every static content or image should be changed keeping few things in mind that width size of the page and height should be dynamic because content used in other languages usually expands out as while I was testing a site designed in English was to be tested in Spanish, when the site was converted into Spanish the whole site gets distorted due to expansion of the text. So this is a major concerned as everything in multilingual site should be dynamic from width to height.

    -Second important thing is that If site has some email templates, I mean email is sent for any notifications than the email templates for every languages should be designed keeping in mind that user of Spain will only understand Spanish language, so a mail in English can hamper the site functionality.

  21. Hi,

    Thanks for the excellent article.
    I wanted some advise from you on my career.
    I am an expert in Japanese language and have good knowledge of C, C++, and Dot Net.
    Currently I am thinking of doing a course in software testing.
    What are the career prospects with my qualification?
    Please could you also suggest some practice resources for the same.

    Thanks in advance,


  22. Hi,

    Thanks for the excellent article.
    This article helped a lot in understanding multi-lingual testing concept.


  23. Respected Sirs and Madams, especially to Mr.Vijay,
    i am sirisha, i am new to testing. whenever i go for some interview they are asking what is “Negative Testing”? and write some nagative test cases for Yahoo login window? please guide me.

  24. Respected Sirs and Madams, especially to Mr.Vijay,
    i am sirisha, i am new to testing. whenever i go for some interview they are asking what is “Negative Testing”? and write some nagative test cases for Yahoo login window? please guide me.

  25. @ sirisha666
    Nagative Testing means testing aimed at showing software doesn’t work properly.
    i am not exactly familiar to write “Nagative test cases for yahoo login window”. i hope some one will soon help you.

  26. hi, in an interview they asked me Nagative test cases for Yahoo log in window. i said nagative test cases are “testing invalid Id,Password”. in 3 interviews i gave same answer, but they refused and said “Testing invalid Id, Password is not Nagative testing and it’s Functional Testing” because,” if we give invalid Id, Password then corresponding error mesage should be displayed” is a Functionality(feature) hence it is Functional Testing. these are not my words, just i faced in interview. help me please.

  27. @sirisha
    hi sirisha, i think you are bothering much about Nagative testing. Actually functional testing is two types. 1. Positive testing 2.Nagative testing. so testing the functionality with nagative intention i.e. test to fail intention is called nagative testing. nagative testing is nothing but testing with invalid data and try to break the system.

  28. @ sirisha666
    see -ve testing is defined as application shd break for corresponding i/p.so ur answer is perfect..dont bother this.
    u r absolutely right..

  29. hi
    can anyone please send me the test cases/tips on
    how to effectively test a social networking website?
    Site is aimed at making families of friends.

  30. I have had the pleasure of testing multi lang applications (office 2007) and websites. I agree with this article. It is best to use two computers side by side (as long as the software are mirror images of eachother). This was, you can have computer which you can refer to when testing i.e. english software and the other being the software tested in another language.

    This makes life a lot easier and means you are able to use the same test scripts over and over on different languages. Hence, meaning you save valuable time not re-creating scripts or localising them for testers. This has the added benifit for companies as they do not need to find additional resources that speak or read the language being tested.

    However, the disadvantage of this is that testers will not be able to determine spelling mistakes within web apps as such and are only performing functionality checks. On the other hand, it is highly recommanded that the scripts are automated to save time and money.

    Good article. Enjoyed reading it.

  31. Please specify, “What is the difference between .com and .co.in” for example google.com and google.co.in.

    That is I know .com is commercial and .co.in for india.

  32. Hello Amit,
    Answer :
    In General for Websites,
    .com is for Commercial Websites Domians
    .in is for india sites Domians
    .uk is for united Kingdom sites Domians
    .us is for United sites sites Domians

  33. Thanks for the seven tips provided for testing multi-lingual websites. Till now, i have tested turkish & Dutch sites along with English verison. Certainly these tips will help me in testing & finding bugs in multi-lingual websites.

  34. Hi, I am a Black Box Tester.
    Currently I am planning to test an application in English (Currently present), French, German, Japanese and Chinese. I have no experience with these languages and I have no idea on how to proceed. Please help.


  35. Hi,
    Thanks for the article it was helpful. I’m testing an application which is deployed in 15+ cultures. Though the through test is done by the people from the specific cultures I would like to simplify this task by automating most (at least the basic things like labels, etc.) items to be tested. Any suggestions on how I can go about doing this?


Leave a Comment