{"id":32843,"date":"2016-02-24T10:47:33","date_gmt":"2016-02-24T05:17:33","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=32843"},"modified":"2016-03-14T10:40:09","modified_gmt":"2016-03-14T05:10:09","slug":"localization-testing-its-best-practices","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/localization-testing-its-best-practices\/","title":{"rendered":"LOCALIZATION TESTING &amp; IT\u2019S BEST PRACTICES"},"content":{"rendered":"<p><strong>What is Localization Testing?<\/strong><\/p>\n<p>Localization testing is performed to verify the quality of a product&#8217;s localization for a particular target culture\/locale and is executed only on the localized version of the product.<\/p>\n<p><strong>Things to know, before you start-<\/strong><\/p>\n<p>In localization testing, an application behaves as expected whether it is for desktop, mobile or online distribution and its process assures the translation accuracy in context after completion of translated text into the user interface, it\u2019s time for testers to take call for application for test drive.<br \/>\nTesting estimate required for the product depends on the number of dialog boxes\/pages to review and on the word count with experienced based testing for localization. Localization involves translation of the app into the local country languages and an ability for the user to see and post content as per various languages or location.<br \/>\nTesting efforts based depend on requirements and complexity of localization feature. Test data provided to Testers should be in detail to get exhaustive and high level test cases from QA Team. There are situations where you may want to do ad-hoc testing, however, formal testing is a necessary step to safeguard quality. Remember, in localization QA, testers have to repeat the same functions according to number of languages. Following Test strategy is better approach to ensure all of them tested the entire product or not.<br \/>\nDue to rapid change in market trends, we need to follow <a href=\"http:\/\/www.tothenew.com\/blog\/agile-developers-vs-agile-software\/\">agile methodology<\/a> to meet the changing requirements and incremental testing approach to localization testing followed by sprint cycle of 2-3 weeks. Frequent validation required for new features across multiple languages and platforms before proceeding for a release. It\u2019s important to be familiar of business goals from localization view. I would like to categorize into: Frequent releases in less time framework, Incremental Testing approach to increase localization efforts, Rapid Development approach for new features.<\/p>\n<p>While deciding the <a title=\"independent software testing services\" href=\"http:\/\/www.tothenew.com\/testing\/automated-independent-manual-testing\">scope of testing<\/a>, these goals create the following challenges for team:<\/p>\n<p>\u2022 While balancing the coverage for functionality ensuring increased test coverage on the new features.<br \/>\n\u2022 Validate User location- ( Location which is stored during registration and will be mapped with content location)<br \/>\n\u2022 Maintaining re-usability of tests across various platform variants<br \/>\n\u2022 Ascertaining test accuracy across repetitive scenarios on multiple languages<br \/>\n\u2022 Make sure of faster execution to uncover defects early on<br \/>\n\u2022 Validate all the features working as per expectation on supported platforms and locales<br \/>\n\u2022 Ensure application is working fine with different versions of the released product.<br \/>\n\u2022 Validate optimized test coverage on all platform variants and supported locales.<\/p>\n<p><strong>Localization Testing &#8211; Characteristics:<\/strong><\/p>\n<p>\u2022 Affected modules such as UI and content<br \/>\n\u2022 Modules specific to region-specific, Culture\/locale-specific and language-specific.<br \/>\n\u2022 Critical Business Scenarios Testing<br \/>\n\u2022 Upgradation and Installation tests run in the localized environment<br \/>\n\u2022 Plan compatibility tests for hardware and application according to the product&#8217;s target region.<br \/>\nLocalization Testing &#8211; UI Testing:<br \/>\n\u2022 Check for Error messages, resource attributes and linguistic errors<br \/>\n\u2022 Typographical errors<br \/>\n\u2022 Validate display environment standards<br \/>\n\u2022 Usability testing of the User interface<br \/>\n\u2022 Validate cultural appropriateness of UI such as colour, design, etc<\/p>\n<p><strong>TIPS &amp; TRICKS:<\/strong><\/p>\n<p>\u2022 For testing application setup a suitable Test environment<br \/>\n\u2022 Follow the correct translation.<br \/>\n\u2022 Start testing with static elements.<br \/>\n\u2022 Follow the correct translation.(You can refer language translation document shared by client and Google translate for verification for sentence)<br \/>\n\u2022 Pay attention to the toast messages and error messages.<br \/>\n\u2022 Ensure that data entry can be done in terms of Localization.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>What is Localization Testing? Localization testing is performed to verify the quality of a product&#8217;s localization for a particular target culture\/locale and is executed only on the localized version of the product. Things to know, before you start- In localization testing, an application behaves as expected whether it is for desktop, mobile or online distribution [&hellip;]<\/p>\n","protected":false},"author":803,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":3},"categories":[1817,1772],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/32843"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/803"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=32843"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/32843\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=32843"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=32843"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=32843"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}